How to Use Additive Schema Changes

Use the following workflow to implement Additive Schema Changes:

In the test environment, complete all development and upgrade testing. The schema.ddl and other *ddl files must be in their final form.
As part of running the Tuning Upgrade Performance process, restore the test environment database to its original, unupgraded state.
Run the Database Configuration Utilities in Apply Additive Schema Changes mode, and generate the schema.additive.sql script.
Windows. You will not be prompted whether you want to run the Upgrade Wizard. Instead, the Upgrade Wizard starts automatically, and creates the schema.additive.sql script. The Upgrade Wizard does not run the script against the database.
UNIX. After the Database Configuration Utilities exit, run the Upgrade Wizard to generate the schema.additive.sql script. The Upgrade Wizard does not run the script against the database.
Review the schema.additive.log file. Verify that the script was created successfully.
Review the schema.additive.sql script. Verify that it will not make changes that conflict with customizations. Edit the script as required.
Use an SQL editor to apply the schema.additive.sql script to the database.
Verify that applications function normally. If necessary, revise schema.additive.sql and reapply it to the database.
Complete the remainder of the Tuning Upgrade Performance process. See Process of Tuning Siebel Upgrade Performance.
When you are ready to upgrade the production database, run the schema.additive.sql script against the production database before doing the production upgrep.
There is no need to then run database statistics. The schema changes are not useful for optimizing applications function before the upgrade.

The steps in this workflow have been incorporated into the process you use to perform both upgrade tuning and the production environment upgrade.

Related Topic