Upgrading data in the Performance History Database

Considerations

The following requirements and limitations apply to the offload upgrading process.

• Db2 Query Monitor 3.4.0 automatically supports all 3.3.0 Performance History Files, 3.4.0 is capable of offloading 3.3.0 Performance History Files. Any 3.4.0 data that is not present is offloaded as default values.
• The Performance History Database table names use the CQM_ prefix. Prior releases used release-specific prefix, for example CQM32_ is used for Db2 Query Monitor 3.3.0. The ability to rename the table names has been deprecated and might be removed in a future release.

Upgrading your Performance History Database

To upgrade your Performance History Database from 3.3.0 to 3.4.0, customize and run highlevel.SCQMSAMP member CQM@CNVT according to the instructions in the member.

CQM@CNVT

This is a LOAD utility job that loads the data from the Db2 Query Monitor 3.3.0 repository tables to the Db2 Query Monitor 3.4.0 tables. The utility statements in this job use the cross-loader function of the LOAD utility to copy data directly from the old tables to the new tables. This job must be run first and can be run repeatedly if necessary. If a failure occurs on one of the LOAD utility statements, rerunning the job allows DSNUTILB to restart the utility at the proper place in the utility stream. The new 3.4.0 objects must be created using CQMDDL (or TCz) prior to running this job.

Upgrading your accelerator data

To upgrade Db2 Query Monitor 3.3.0 accelerator tables to Db2 Query Monitor 3.4.0 accelerator tables, you must first create the 3.4.0 accelerator tables and then customize and run highlevel.SCQMSAMP member CQMMIDAA according to the instructions in the member. After you run CQMMIDAA, if your target is accelerator shadow tables (not accelerator-only tables) for Db2 Query Monitor 3.4.0, customize and run highlevel.SCQMSAMP member CQMIDAAL according to the instructions in the member.