Diagnosing and Tuning Database performance
IBM® Sterling Control Center Monitor relies heavily on its database to provide functionality. Slowness in database queries such as inserts, updates, and deletes signal database performance issues. To confirm database performance issues are occurring you may run the following text-based searches in the IBM Sterling Control Center Monitor Engine logs:
Messages logged with this text appear as follows:
CCTR135I Time to insert monitored server data into EVENTS database table was: 436776 milliseconds
CCTR138I Time EventMonitor took to retrieve data from EVENTS database table was: 1254366 milliseconds
updateQueuedProcesses query time excessive
updateQueuedProcesses query time (t1-t0) excessive - Total time
ProcessSummaryWorker.getEvents() logic took an inordinate amount of time!
Time to update nnn processes as ended was excessive.
ProcessSummaryWorker took an inordinate amount of time to summarize file transfer
ProcessSummaryWorker took an inordinate amount of time to summarize Process
ProcessSummaryWorker took an inordinate amount of time to commit database changes to CC_PROCESS and CC_FILE_TRANSFER
These messages are indicative of:
- Databases whose indices are not being maintained on a regular basis and/or
- Databases that hold too much data in them
Database inserts and updates should typically take just a few milliseconds. If the queries take too long, ensure the Control Center Monitor table indices are being maintained on a regular basis.