After SSIM MR2 Migration - SQL1477N Table SYMCMGMT.STO2_0_SAVLATEST" cannot be accessed. SQLSTATE=55019

Article:TECH89113  |  Created: 2008-01-06  |  Updated: 2008-01-29  |  Article URL http://www.symantec.com/docs/TECH89113
Article Type
Technical Solution


Issue



After upgrading to MR a large number of default reports that use SYMCMGMT.STO2_0_SAVLATEST table are not working. This procedure is a workaround, the permanent fix is to apply MR3 to a 4.5 SSIM or move to SSIM 4.6.

Symptoms
When running DB2 in command line you get the following message


db2 => select * from symcmgmt.sto2_0_savlatest

SNAPSHOT_ID SNAPSHOT_MACHINE

VIRUS_DEFINITIONS PARENT_VIRUS_DEFINITIONS USER_NAME

ALT_NETWORK_ADDRESS
MACHINE_TYPE_ID SAV_DOMAIN
PARENT

CLIENT_GROUP

PRODUCT_VERSION MACHINE_IP
CLIENT_GOOD CHECK_IN
--------------------------------------- ----------- --------------------------
SQL1477N Table "SYMCMGMT.STO2_0_SAVLATEST" cannot be accessed.
SQLSTATE=55019



Another select on this table fails:

db2 => select PRODUCT_VERSION as "Client Version", count(PRODUCT_VERSION) as
"Total Client Count" from symcmgmt.sto2_0_savlatest group by PRODUCT_VERSION


Client Version Total Client Count
---------------------------------------------------------------- ------------------
SQL1477N Table "SYMCMGMT.STO2_0_SAVLATEST" cannot be accessed.
SQLSTATE=55019




Solution



As a workaround, please run attached script as below. The script will stop the eventservice, recreate the table, restart the eventservice.

Detailed steps:
As db2admin user,

1) Get two files from the attachment and copy over to appliance.
create_sto2_0_savlatest.sh
create_sto2_0_savlatest_table.sql

2) Convert to unix format.
dos2unix create_sto2_0_savlatest.sh
dos2unix create_sto2_0_savlatest_table.sql

3) Run the script file.
chmod 777 create_sto2_0_savlatest.sh
./create_sto2_0_savlatest.sh



create_sto2_0_savlatest.sh
create_sto2_0_savlatest_table.sql





Supplemental Materials

SourceETrack
Value1225839

Legacy ID



2008030611182054


Article URL http://www.symantec.com/docs/TECH89113


Terms of use for this information are found in Legal Notices