IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Upgrade from a previous installation > Plan your upgrade
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Upgrade the warehouse from IBM Tivoli Monitoring V6.1.x levels
Complete these steps only if you are upgrading from IBM Tivoli Monitoring V6.1.x levels. They do not apply to any level after and including V6.2.0. Running the upgrade scripts again may lead to loss of some data.
Some of the monitoring agents have made changes to the warehouse tables. There are three types of changes, two of these types of changes require performing upgrade procedures before running the V6.3 Warehouse Proxy and Summarization and Pruning Agents. The procedure for the other change can be performed before or after you upgrade IBM Tivoli Monitoring. These procedures are accomplished using product-provided scripts.
Case 1 changes affect the table structure, and Case 3 changes affect the table location. Both Case 1 and Case 3 changes must be completed before running the 6.3 Warehouse Proxy and Summarization and Pruning Agents. These changes and procedures are documented comprehensively in the following user's guide appendix for each monitoring agent that is affected: "Upgrade: upgrading for warehouse summarization."
- Case 1 changes add a new column to a raw table, and assign a default value to the column. If the 6.3 Warehouse Proxy Agent is started before these scripts are run, a NULL default value is assigned, and that default value cannot be changed. The following monitoring agents have Case 1 changes:
- Monitor for Databases: DB2 for Linux, UNIX, and Windows Agent
- Monitor for Applications: mySAP Agent
- Monitor: UNIX OS Agent
- Monitor: Windows OS Agent
- Case 2 changes affect how agent data is summarized because of changes in primary key definitions. The Case 2 changes can be done before or after you upgrade IBM Tivoli Monitoring. The following monitoring agents have Case 2 changes:
- Monitor for Applications: mySAP Agent
- Monitor for Databases: Sybase Server Agent
- Monitor: Windows OS Agent
- Case 3 changes are only applicable if you are using DB2 for Linux, UNIX, and Windows as your warehouse database. These changes move a summary table from the 4K table space to the 8K table space. If the 6.3 Summarization and Pruning Agent is started before these scripts are run, you receive DB2 for Linux, UNIX, and Windows errors, because the row size of the upgraded table is longer than what can fit into the 4K table space. The following monitoring agents have Case 3 changes:
- IBM Tivoli Monitoring for Databases: DB2 for Linux, UNIX, and Windows Agent
- IBM Tivoli Monitoring for Databases: Oracle Agent
- IBM Tivoli Monitoring: UNIX OS Agent
To ensure that you can make the table upgrades required by Case 1 and Case 3 before installing the 6.3 monitoring agents, do the following:
- Stop the Warehouse Proxy and the Summarization and Pruning Agents prior to upgrading IBM Tivoli Monitoring.
- Change the default startup of these monitoring agents to "Manual" so they do not start automatically during any restart of host computer. This prevents these agents from starting automatically during the upgrade process.
- Perform the IBM Tivoli Monitoring upgrades.
- Make the warehouse updates for the monitoring agents with Case 1 and Case 3 changes as described in the user's guide for the affected agent.
- Re-enable the automatic startup of the Warehouse Proxy and the Summarization and Pruning Agents, and start these agents.
Several monitoring agents made changes to the warehouse collection and summarization characteristics for some agent attribute groups. These changes correct and improve the way warehouse data is summarized, producing more meaningful historical reports. For an explanation of these changes and the implications to your warehouse collection and reporting, see the "Upgrading for warehouse summarization" appendix of the user's guide for your specific monitoring agent.
Parent topic:
Plan your upgrade