1. Database Upgrade Guide
  2. Production Environment Upgrades

Production Environment Upgrades

After you have completed testing applications and have tuned the upgrade SQL commands, you perform the production upgrade. The production upgrade uses the SQL commands generated in the test environment. In the test environment, you perform the following steps to upgrade your production environment Siebel database:

  1. ODBC Connection. Define an ODBC connection to the production environment Siebel database

  2. Apply Additive Schema Changes. This step is optional and is run in the production environment. You can run this mode of the Database Configuration Utilities without taking the database offline. This mode makes schema changes that do not affect the operation of the application. This reduces the amount of time the production database must be offline to perform the upgrade.

  3. Prepare for Production. This step is not required. You ran it as part of the test environment upgrade. The required changes have already been made to the upgrade SQL commands.

  4. upgrep. Run the Database Configuration Utilities in the test environment. Enter information for the production environment (not the test environment), including the new ODBC definition.

    The Database Configuration Utilities update the upgrade configuration file with production environment information. A lock file that was set when you ran the utility previously, prevents new SQL from being generated. This preserves the SQL you have revised and tuned.

    When you run the Upgrade Wizard, it reads the production environment information from the configuration file and uses the test environment SQL commands to upgrade the production environment Siebel database.

    The upgrep step makes the same changes as when it ran in the test environment. This includes automatically running the production upgphys portion of the upgrade.