DB2 Version 9.7 for Linux, UNIX, and Windows

FP5: Diagnosing upgrade problems is easier

Troubleshooting problems that arise from unsuccessful upgrades is now made easier by support for the collection of diagnostic data before the upgrade operation. You can collect data before upgrading by specifying the new -preupgrade parameter for the db2fodc command and the db2support command. You can collect additional data after the upgrade operation to help troubleshoot an instance creation problem by specifying the new -clp parameter for the db2fodc command. Data that the -preupgrade parameters collect provide insight into the system environment and data server software as they were before the upgrade operation.

To collect the data using the -preupgrade parameter, first issue the db2fodc -preupgrade command. Next, issue the db2support -preupgrade command to collect the data from the db2fodc -preupgrade command and store it in the db2support_preupgrade.zip archive file. If a post-upgrade problem that requires opening a problem management record (PMR) occurs, you can send the db2support_preupgrade.zip file to IBM technical support to make the troubleshooting process easier.

To diagnose a problem that occurred during an instance creation, you can use the -clp parameter by issuing the db2fodc -clp command. This command quickly collects environment and configuration related information and stores it in a new directory created under the current diagnostic path, or under a path that you specify. This information makes troubleshooting the instance creation problem easier.