Upgrade the Siebel Database (upgrep and upgphys)

You do not run the upgrep and upgphys portions of the upgrade in the production environment. Instead, the numbered steps in this topic implement the following process:

• Run the Database Configuration Wizard in the production environment.

• In the utilities, enter the information for the production environment instead of the test environment. For example, you enter the ODBC connection for the production environment.

  This information configures the driver file to run against the production database rather than the test database. It also configures the driver file to use the upgrade SQL files you generated for the test upgrade.

• Run the Upgrade Wizard. The Upgrade Wizard uses the SQL files in the test environment to upgrade the database in the production environment.

  This approach has several advantages:

• You do not have to generate upgrade SQL files in the production environment, and then manually transfer the customizations to them from the test environment.

• You do not lose any changes to the SQL files that were made by Siebel Upgrade Tuner in the test environment.

• You do not have to run the Database Configuration Wizard in Prepare for Production mode again.

• With some exceptions, you do not have to perform again the database-related configuration tasks required by Siebel Release Notes on My Oracle Support or Articles on My Oracle Support.

If your network configuration prevents creating an ODBC connection to your production database from inside your test environment, then contact Oracle Global Customer Support for assistance in completing the production upgrade.

1. Verify that you have a current backup of the production environment database.

2. On the Siebel Server you used to upgrade the test environment, create an ODBC to connect to the production environment database.

3. Navigate to DBSRVR_ROOT\common (UNIX: DBSRVR_ROOT/common) and verify that the file sqlgen.usg exists.

   This file contains a record of when the SQL generator was run. When you run the Database Configuration Wizard, if this file exists, then no SQL commands are generated.

   Caution: If this file does not exist, then do not run the Database Configuration Wizard. The Database Configuration Wizard will overwrite the SQL files used to upgrade your test database. Contact Oracle Global Customer Support for guidance on proceeding with the upgrade.

   You do not have to run the Database Configuration Wizard in Prepare for Production Mode.

4. (Optional) Changing the Siebel Database Configuration Utilities Language.

5. Run the Database Configuration Wizard:

   • Preparing to Run the Siebel Database Configuration Wizard

   • Running the Siebel Database Configuration Wizard on Windows

   • Running the Siebel Database Configuration Wizard on UNIX

   1. Choose the following settings when you run the utility:

      • Upgrade Options. Upgrade Siebel Database Schema (upgrep and upgphys)

      • Environment Type. Production

   2. Enter the information for the production environment instead of the test environment.

   3. Enter the name of the ODBC for connecting to the production database.

   4. When prompted whether you want to run the Siebel Upgrade Wizard, answer No and exit.

      This updates the primary UCF file with the production environment configuration. When you run the Siebel Upgrade Wizard, the SQL commands will be executed on the production environment database.

6. In the test environment, verify that the SQL scripts for performing the upgrade were not overwritten. You can do this by checking the modification times. If the scripts were overwritten, then do not continue. Instead, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle’s Application Expert Services.

7. Perform the production database upgrade. See Starting the Siebel Upgrade Wizard.

   The Siebel Upgrade Wizard uses the SQL commands generated for the test environment to upgrade the production environment. If you used Upgrade Tuner to revise the SQL commands, then these changes are included.

8. Review the upgrade logs and resolve errors: Reviewing Siebel Upgrade Log Files for Errors.

9. If the upgrade contains unacceptable errors, then do the following:

   1. Restore the backup of the database.

   2. Correct the errors.

   3. Rerun the Siebel Upgrade Wizard.

10. Manually Archiving Siebel Upgrade Log Files.

11. Use the Siebel Application Deployment Manager to migrate administrative data such as LOVs and responsibilities from test to production.

12. Back up the upgraded production environment database.