Upgrade the Siebel Database Schema (upgrep + upgphys)

If you have completed a production test upgrade and have tuned the SQL and JCL upgrade files on the z/OS host, you can use these files to perform the target database upgrade in the production environment. This approach has several advantages:

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

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

• You do not have to run the zSeries Staging of Files for Upgrade process using the Database Configuration Wizard to create the staging database and to generate upgrade files again.

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

Note: Before using the tuned upgrade files that you generated in the production test environment, you must edit the upgrade files to change the production test environment values to production environment values.

To upgrade the Siebel database schema:

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

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

3. Edit the tuned upgrade files you generated during the production test environment upgrade. Replace any values in the upgrade files that are specific to the production test environment with production environment values. You might have to change the following values in the upgrade files:

   • Host/LPAR name where the target database resides

   • DB2 subsystem name of the target database

   • Schema/Tableowner qualifier name on the target database

   • ODBC data source name of the target database

   You can edit the upgrade files using any utility that allows you to edit partitioned data sets (PDSs). For advice on editing upgrade files, contact your Oracle sales representative for Oracle Advanced Customer Services.

4. Upgrade the target database using the tuned upgrade files, which now contain production environment information, by performing the following tasks:

   1. Dropping Partitioned EIM Tables.

   2. Applying Additive Upgrade Changes to the Target Database.

   3. Renaming the Production Environment Repository.

   4. Performing the In-Place Target Database Upgrade.

5. Extract the storage control file from the target database using the Database Configuration Wizard as follows:

   • Specify the following values when prompted to do so:

     • Extract Options: Extract from Catalog.

     • Storage Control File: Specify the name of the storage control file to be extracted. You must specify the name storage_postupg.ctl.

   • Make sure you specify values for the target database when prompted for the names of the schema Qualifier, ODBC data source, and database user name and password.

     The procedure to extract a storage control file using the Extract From Catalog option is described in Implementing Siebel Business Applications on DB2 for z/OS. The extracted target database storage control file is used as input to the upgphys upgrade process.

6. Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data.

7. Activating New License Keys After an Upgrade.

8. About the Siebel Upgrade Log Files.

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

   1. Restore the backup of the database.

   2. Correct the errors.

   3. Rerun the Database Configuration Wizard.

10. Manually Archiving Upgrade Log Files.

11. Back up the upgraded production database.

12. Deleting Redundant Upgrade Files.