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
SQL Server ASM reports a server with status of running in the sqlsvrSvrDescTable after the server has been shutdown Customer is trying to use ASM for MS SQL server.When the SQL server is down so that alert will be generated. However when they shut down the ms sql server the sqlsrvDescTable.status still shows as running . I found the similar issue 20097,033,866 in CAST and found couple of information: 1. APAR logged IY95967/NBS049797: The subagent does not monitor Microsoft SQLServer 2005 correctly. APAR Status :Fix for this is available in fix pack 3.2.0-TIV-SSM-LA0748 and above. 2.Fits logged for ssm 4.0v > MR0706072258 Fits Status: Available Developer had set up a test environment and tested the customers scenario. This problem does seem to exist in FP4. Hence creating a NEW APAR
Local fix
recommend installing the latest GA fixpack 4: http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg24018968
Problem summary
**************************************************************** USERS AFFECTED: SSM 4.0 on Windows (Netcool/ASM for SQLServer) **************************************************************** PROBLEM DESCRIPTION: The problem was that the stsqlsvrSvrDescStatus value was never being updated when the connection to the server was lost, even though you could tell it happened because sqlsvrServerConnectionStatus goes to disconnected. **************************************************************** RECOMMENDATION: Upgrade to Fix Pack 7 for SSM 4.0 ****************************************************************
Problem conclusion
The solution was to implement a (partial) row update on every sample (sqlsvrServerUpdateInterval) even if the connection failed. In this case, sqlsvrSvrDescStatus will now change to unknown(8) for lack of a better option available in the MIB. For the same reason, more detailed error diagnosis has not been implemented. Only running(3) and unknown(8) states are implemented. If the subagent has NEVER successfully connected then there will be no sqlsvrSvrDesc row. The unknown(8) state means that the connection used to exist but does not exist at present. The fix for this APAR is contained in the following maintenance packages: | fix pack | 4.0.0-TIV-SSM-FP0007
Temporary fix
Comments
APAR Information
APAR number
IZ39277
Reported component name
NETCOOL SYS SVC
Reported component ID
5724P4300
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-12-09
Closed date
2009-02-06
Last modified date
2009-02-06
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 PSN
UP
Document Information
Modified date:
06 February 2009