Upgrade Guide for DB2 UDB for z/OS and OS/390 > Tuning the Upgrade Scripts >

Deactivating SQL that Affects No Data

Upgrades: All upgrades.

Environments: Production environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

You must analyze your customizations and the nature of application data before you deactivate SQL statements that appear to affect zero rows. Do not deactivate zero-row SQLs on an empty or low-volume database. Use an exact copy of your production database, instead.

The upgrade scripts may contain SQL statements that run against all tables whether or not the tables contain any data. Such SQL executions may be redundant for your production upgrade. You can use the Siebel Upgrade Tuner to analyze, edit, and deactivate SQL statements that do not affect any data, thereby slowing the upgrade process.

The Siebel Upgrade Tuner contains four screens that you access by clicking on tabs:

• Process Information. This screen displays information retrieved by the Upgrade Tuner from the summary.xml file.
• Parallelize Table Creation. This screen allows you to parallelize table creation.
• Parallelize Index Creation. This screen allows you to parallelize index creation.
• Deactivate 0-Row SQLs. This screen displays SQL statements that run against tables without any data. You can selectively review these SQL statements, and if they are unnecessary, you may deactivate them for your production upgrade.

For more information on the Upgrade Tuner, see About Tuning the Production Upgrade Scripts.

Prerequisites: For UNIX platforms, you must first transfer files to the Windows platform. See Transferring UNIX Files for Use by Upgrade Tuner.

To identify and deactivate SQL statements that affect zero rows

1. Launch the Upgrade Tuner.
2. Click on the Deactivate 0-Row SQLs tab in the Siebel Upgrade Tuner.

   The Deactivate 0-Row SQLs screen appears.

   The Deactivate 0-Row SQLs screen only provides information for native SQL (not for odbcsql).

3. Inactivate an unnecessary zero-row SQL statement by clicking the check box for that statement in the Inactive column.
   • A check mark in the Inactive column indicates that the associated SQL statement is inactive and therefore not upgraded. The word changed appears beside the check box to indicate that the status changed.

     Before deactivating a particular SQL statement, review it by scrolling through the comment field at the bottom of the screen, and then evaluate the safety of deactivating this statement. Make sure you are not deactivating SQL that is necessary for your upgrade.

   • To return all deactivated SQL statements to an active upgrade state (such as statements deactivated while tuning a previous upgrade), click Activate All.