Test Additive Schema Changes
If you do not plan to run additive schema changes on the production database in the production environment, then you do not need to perform the steps in this topic.
Perform these steps on the target database.
(Optional) Changing the Siebel Database Configuration Utilities Language.
In the test environment, run the Database Configuration Wizard:
Choose Apply Additive Schema Changes mode.
The Apply Additive Schema Changes mode identifies changes that can be made to the target 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 target database.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.sql
script. It does not run the script against the target database.Run the SQL script against the target database.
Thoroughly review the operation of all applications. Verify that applying the additive schema changes has not adversely affected the operation of all applications.
If applying additive schema changes adversely affects the operation of the applications, then do the following:
For help diagnosing the cause of the problem and help in taking corrective action create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers remain the same and are listed on My Oracle Support.
Restore the target database from backup before proceeding with further upgrade tuning.
Do not use the additive schema changes feature during your production upgrade.
If applications function normally, then continue with upgrade tuning. Consider using the additive schema changes feature during your production upgrade.