A new IF for TBSM v4.1.1 is now available here. TBSM v4.1.1 IF001 and IF004 are dependencies.
This Interim Fix addresses problems reported in IBM Tivoli Business Service Manager 4.1.1.
* APARs that are included in this Interim Fix:
IZ17042 MOSWOS TBSM AGENT MONITORS INCORRECT OMNIBUS UNIX PROCESS
TBSM Process Control Agent does not accurately reflect status of the process control agent. Regardless of whether the process control daemon is up or down, it shows as Down in the Process
Control Agent view of the TBSM Agent workspace.
IZ17159 THE DIRECTSQL FUNCTION SI NOT AVAILABLE BY DEFAULT FOR POLICY WRITING.
The option to use this function by default is not provided for policy writing in the ESDA Edit Policy window.
IZ15468 SERVICE INSTANCE IN MAINTENANCE TURNS GREEN BEFORE MAINTENANCE
A service in maintenance state should remain blue color, until the maintenance schedule is complete, However, if an event comes in that clears the service, the service instance and status in the
Services tree turns green (not staying blue until maintenance is complete).
IZ15409 WHEN TBSM CHECKS THE STATUS OF THE DATABASE, IT CAN CAUSE THE DATABASE TO CRASH
After TBSM runs for a while, the status of the database is checked and TBSM crashes with the following error in the RAD_server.log file:
ENTRY RADService::executeNcs_dbCommand:command=/opt/netcool/bin/rad_db status
RADService::executeNcs_dbCommand: os.name=Linux
RADService::executeNcs_dbCommand: Exception: java.io.IOException:
Too many open files
Thread[CheckDBStatusThread,5,main]:
java.io.IOException: java.io.IOException: Too many open files
at java.lang.UNIXProcess.
at java.lang.ProcessImpl.start(Unknown Source)
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at com.micromuse.sla.impact.RADService.executeNcs_dbCommand(Unknown Source)
at com.micromuse.sla.impact.RADService$CheckDBStatusThread.run(Unknown Source)