Readmes are available
IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001
APAR status
Closed as program error.
Error description
console commands automatically written to agent.state are semantically incorrect for Oracle ASM
Local fix
1. Remove "oracle var=value" from agent.state 2. In the console run "set restore off", or if the SSM is not running, in init.cfg set "RestoreState=off" 3. Make any Oracle ASM configuration changes desired in oracle.cfg only.
Problem summary
There were three issues present, firstly the assign, consistent and commit semantics of the oraInstanceTable were incorrect. This resulted in us getting wrongValue errors rather than inconsistent errors. Secondly the configuator support library was incorrectly processing all columns in the table every time one was set. This meant than when Monitoring was set to yes, and the datacontrol was being set, the agent.state file registered errors as the rows like sid, user name and password were being set again. Thirdly, indexes were not being preserved when the config was being saved. This effectively meant that the config for database instances after the first was not being restored.
Problem conclusion
SNMP semantics were resolved so that that that consistency checks were done at the appropriate time. Made sure that the oraInstanceTable index was written to the agent.state file. Finally the configurator only sets one object per command and not all objects as this resulted in multiple sets which caused errors to be reported when there weren't ones and was also inefficient.. The fix for this APAR is contained in the following maintenance packages: | fix pack | 4.0.0-TIV-SSM-FP0004
Temporary fix
Comments
APAR Information
APAR number
IZ21224
Reported component name
NETCOOL SYS SVC
Reported component ID
5724P4300
Reported release
320
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-05-02
Closed date
2008-05-22
Last modified date
2009-01-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
NETCOOL SYS SVC
Fixed component ID
5724P4300
Applicable component levels
R400 PSY
UP
Document Information
Modified date:
05 January 2009