Apply Additive Schema Changes

These steps are optional. Perform these steps only after you have thoroughly tested the additive schema changes feature in the test environment and have verified that it will not adversely affect your applications.

Perform these steps on the production database. You do not need to take the production database offline. You can perform these steps anytime prior to running the production upgrep.

After applying additive schema changes there is no need to run database statistics. The schema changes do not affect the performance of your release prior to the upgrade.

1. Review About Siebel Additive Schema Changes Mode.

2. Verify that you have a recent backup of the production database and that you are logging transactions.

   If you encounter problems applying additive schema changes, then you might need to restore the production database.

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

4. In the production environment, start 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

5. Choose Apply Additive Schema Changes mode.

   The Apply Additive Schema Changes mode identifies changes that can be made to the production database without taking it offline.

   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 production database.

6. UNIX. Run the Siebel Upgrade Wizard.

   See Starting the Siebel Upgrade Wizard.

   Specify master_additive_gen.ucf as the input file.

   The Upgrade Wizard generates the schema.additive.sqlscript. It does not run the script against the production database.

7. Run the SQL script against the production database.

   See Applying Siebel Additive Schema Changes.

8. Thoroughly review the operation of all applications. Verify that applying additive schema changes has not adversely affected applications function.

9. If you are applying additive schema changes adversely affects the operation of the application, then do the following:

   1. Contact Oracle Global Support for help in diagnosing and correcting the problem.

   2. If required, restore the production database from backup.