Perform Upgrade Tasks (Production Test Environment)

This phase upgrades a production test environment Siebel database to the new release allowing you to test how customizations work with the new release and to tune the upgrade scripts.

Caution: You are required to contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance with tuning your upgrade scripts. If you do not, you might invalidate your support agreement.

This phase includes the following tasks:

  • Prepare application data. These tasks are about preparing application data for migration.

  • Prepare for Production Upgrade (Upgrades from 7.5.3 only): Run the Database Configuration Wizard in Prepare for Production Upgrade mode. This mode compares the repository schema and the physical database schema and generates a file, SCINDX.SQL, which is used to remove obsolete indexes. SCINDX.SQL lists indexes present in the physical schema that are not present in the repository schema.

    Note: You must define an ODBC connection to the development environment database before performing this upgrade step.
  • Upgrade database (upgrep + upgphys). Run the Database Configuration Wizard in upgrep + upgphys mode, selecting the zSeries Staging of Files for Upgrade option. This generates the files required to build the staging database and generate the upgrade files required to perform the in-place upgrade of the database. The additive and nonadditive schema upgrade files are generated separately.

  • (Optional) Apply the additive upgrade files to upgrade the database. This is a nondisruptive upgrade process.

  • Perform the in-place upgrade of the database. The following changes are made during this phase of the upgrade process:

    • Drops interface tables and database triggers

    • Populates columns that must change from NULL to NOT NULL

    • Uses the schema.ddl file 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

    • Updates primary children foreign key references

    • Performs miscellaneous file actions

    • Makes several administrative changes to table data, including updating the schema version in S_APP_VER.

  • Upgrade the repository and import seed data (upgrep + upgphys). Run the Database Configuration Wizard in upgrep + upgphys mode again, selecting the zSeries Seed/Repository Upgrade option to complete upgrade processing. During this step, the upgraded repository and seed data are imported.

  • Tune upgrade scripts (optional). You can improve the performance of the production environment upgrade by tuning the production upgrade scripts in the test environment.

    Run several production upgrades against the test database. This allows you to understand the upgrade process before performing the production upgrade, to conduct performance testing, and to fine tune the upgrade scripts. After carrying out thorough performance testing, you can perform the live production upgrade using the tuned upgrade files.