Process of Upgrading the Target Database

Upgrades: All upgrades.

Environments: All environments

This topic is part of an upgrade process. See Performing a Siebel Database Upgrade.

After you have generated upgrade files against the staging database and prepared the JCL used to run the upgrade processes, you are ready to perform the target database upgrade. This involves the following steps:

1. Dropping Partitioned EIM Tables

2. Creating and Loading Siebel Log Tables

3. (Production upgrades only) Applying Additive Upgrade Changes to the Target Database

4. (Production upgrades only) Renaming the Production Environment Repository

5. Performing the In-Place Target Database Upgrade

For production database upgrades, the additive changes applied to the staging database are applied to the production target database as part of the preupgrade process. The remaining nonadditive, schema, unload, load and data migration processes are then applied to the target database as part of the critical path in-place upgrade.

For development database upgrades, upgrade changes are applied in one step to the target database during the in-place upgrade.

Note: The procedures in this chapter use Siebel-Scheduled job execution. For information on job scheduling options, see Executing Jobs Using Siebel-Scheduled Mode or Vendor-Scheduled Mode.