Siebel Database Upgrade Guide > Upgrading the Siebel Database >

Applying Siebel Additive Schema Changes

Upgrades from: All Supported Siebel releases.

Environments: Production test, production.

All databases. This topic applies to all supported databases.

Windows and UNIX only. This topic does not apply to IBM z/OS platforms.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

As of Siebel CRM 8.0, you can run Database Configuration Utilities in Apply Additive Schema Changes mode. This generates a schema.additive.sql script that makes schema changes to the Siebel Database schema. You do not have to take the database offline to apply this script.

Applying this script to your production database reduces the number of upgrade steps that must be performed while the production database is offline. This reduces production database downtime during the upgrade.

The recommended method for using this feature is to first test it in the production test environment as part of upgrade tuning. After verifying that schema.additive.sql does not adversely affect the operation of the application, you then run the script against the production database.

Prerequisites for Applying Siebel Additive Schema

  • You must have run the Database Configuration Utilities in Apply Additive Schema Changes mode to generate the schema.additive.sql script.
  • You must have reviewed the Apply Additive Schema Changes log file and verified that schema.additive.sql was generated without errors.
  • If you are testing the script in the production test environment, the schema of the Siebel Database should be the same as the schema of the production environment Siebel Database.

To apply additive schema changes

  1. Navigate to the directory where schema.additive.sql is located.
  2. Review the script and verify that it does not make unacceptable changes to the schema.
  3. Production environment only. Compare the script generated in the production environment with the one generated in the production test environment. If the scripts are not identical, determine why. If you cannot determine that the differences are benign, do not apply additive schema changes in the production environment.
  4. Using any SQL editor, run the script against the Siebel Database.

    You can run schema.additive.sql multiple times. For example, you can run the script, revise it, and run it again.

Related Topics

About Siebel Additive Schema Changes Mode

Siebel Database Upgrade Guide Copyright © 2008, Oracle. All rights reserved.