1. Database Upgrade Guide
  2. Test Environment Upgrades

Test Environment Upgrades

For a test environment upgrade, you run the utility three times:

  1. Prepare for production.

    Note: This topic is only applicable for upgrades from Siebel CRM release 7.5.3. For upgrades from later releases, you do not have to perform this step.

    This mode does the following in the test database:

    • Examines the development environment database and generates SQL that deduplicates intersection tables and sets up support for database aggregation.

      In the test environment, you must define an ODBC connection to the development environment database before performing this upgrade step.

    • Compares the repository schema and the physical database schema. Generates a file that lists indexes present in the physical schema that are not present in the repository schema. You can decide whether to remove these indexes.

  2. upgrep. This mode makes the following changes:

    • Removes interface tables and database triggers

    • Populates columns that must change from NULL to NOT NULL

    • Uses the custrep.dat and *ddl files from the development environment upgrade to create new tables and merge existing tables

    • Prepares for index creation. Verifies that there are no unique key violations.

    • Creates indexes

    • Imports seed data

    • Updates primary children foreign key references

    • Performs miscellaneous file actions

    • The upgphys portion runs automatically. It makes several administrative changes to table data, including updating the schema version in S_APP_VER.

  3. Upgrade Tuning. These steps are optional. You can use the Logparse utility to tune the SQL generated for the upgrade. Logparse identifies SQL commands that are not used, or that can be run in parallel. This reduces the time required to perform the production database upgrade.

You can also test the Additive Schema Changes script to verify that it does not adversely affect the operation of the application. Additive Schema Changes allows you to run part of the schema upgrade without taking the database offline. This reduces production database downtime.