IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Post-deployment phase > Applying maintenance
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Post-upgrade health check
Use the following checklist for your post-upgrade health check.
- Check if the predefined and user-created workspaces that were present prior to the upgrade are still in place.
Log in to the portal server using the portal browser or desktop client and browse through the different workspaces for each product type.
- If you enabled the self-describing agent capability for your upgrade, run the tacmd listappinstallrecs to ensure that all products upgraded by the self-describing agent feature completed the installation without errors. Check the Audit Log messages for the Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server to ensure there are no self-describing agent errors related to the latest product upgrades.
- Check if the predefined and user-created situations that were present prior to the upgrade are still in place.
Log in to the portal server using the portal browser or desktop client and browse through different situations in the Situation Editor or run the tacmd listsit command.
- Check if all the catalogs are the same on each monitoring server (hub and remote). Try one of the following two approaches:
- Run grep on each monitoring server (hub and remote). For example:
grep @ * | awk ’{print $2, $3, $4, $5}’ | sort
- Run the following SQL against each monitoring server in a portal server view:
"SELECT APPL_NAME, TIMESTAMP FROM SYSTEM.SYSAPPLS AT (’REMOTE_TEMS’) ORDER BY APPL_NAME"
Check if the depots populated on each monitoring server (hub and remote) are the same. Run these commands from the hub monitoring server.
Check if the warehouse data is visible through the workspace views, meaning the portal server still has the correct connection to the warehouse database. Select the attribute group for which history collection is enabled by checking that view and making sure the data can be pulled for more than 24 hours.
Check if the agents are online and connected to the expected remote monitoring server. Run the tacmd listsystems command.
Check if the situations are firing and events are being forwarded to Tivoli Enterprise Console or OMNIbus. Run the command on the Tivoli Enterprise Console server using wtdumprl or drag the Tivoli Enterprise Console icon to any view to view the events.
Check if the historical configuration is active. Log in to the portal server using the portal browser or desktop client and click History Configuration. Browse through the desired attribute groups to see if they are still active.
Or you can run this query: "SELECT NODEL, OBJNAME, LSTDATE FROM O4SRV.TOBJACCL WHERE OBJNAME LIKE 'UADVISOR*'"
Check if the Warehouse Proxy Agent and Summarization Pruning Agent are correctly started, meaning the agents made successful connections to the warehouse database. You can examine the WAREHOUSELOG table to see the last updates by each attribute group. See sample below:
SELECT ORIGINNODE AS "Agent Hostname", OBJECT AS "Attribute Group", EXPORTTIME AS "Export Time", ROWSRECEIVED AS "Received Rows", ROWSINSERTED AS "Inserted Rows", ROWSSKIPPED AS "Skipped Rows", ERRORMSG AS "Error Message" FROM WAREHOUSELOG
Note to Windows users: If you attempt to run a tacmd CLI command and either the Embedded Java Runtime or the User Interface Extensions are not available on the node where you invoke the command, you will receive the error shown in Figure 1. If this happen, complete the procedure outlined in Install the Embedded Java Runtime and the User Interface Extensions and retry the tacmd command.
Parent topic:
Applying maintenance