Managing Zero-Row SQL Commands Using Siebel Upgrade Tuner
Environments: Test environment only. Does not apply to production environment.
Platforms: Windows and UNIX only.
Databases: All databases.
The upgrade scripts support all the tables in the Siebel data model. This support means the tables might contain SQL commands that run against tables that are not included in your Siebel database, that are empty, or do not contain data that applies to a specific SQL command. By inactivating such SQL commands, you can reduce the time required to perform the production upgrep.
The Deactivate 0-Row SQLs page displays a list of SQL files that contain commands that returned zero rows. This means the command does not affect any data and does not change the database schema. The screen displays only upgrade commands executed natively by the RDBMS. The screen does not display SQL commands executed using odbcsql.
The SQL files are located in DBSRVR_ROOT\DBPLATFORM\upgrade\VERSION, for example, db2\upgrade\V8_x.
When you select a file, the command that returned zero rows displays in the lower half of the screen. You can then either deactivate or activate the command. You cannot edit the displayed command.
When you deactivate a command and save your changes, Upgrade Tuner
opens the SQL file containing the command and inserts (Execute=No) in the command. When you activate a command, Upgrade Tuner removes (Execute=No) from the command.
Requirements
In the test environment, you must have completed the production upgrep step.
You must have run the Logparse utility on the production upgrep log files. See Summarizing Siebel Log Files Using the Logparse Utility
For UNIX platforms, you must have transferred files to a Windows host on which a Siebel Server is installed. See Transferring UNIX Files for Use by Siebel Upgrade Tuner
Analyze your customizations and the nature of application data. Verify that you understand the role of any new tables you have added.
Start Upgrade Tuner. See Starting and Stopping Siebel Upgrade Tuner