1. Database Upgrade Guide
  2. Production Environment

Production Environment

The production environment is your live business environment, where your internal and external users interact with applications and generate business data. Production instances are also Runtime Repository (RR) environments relying on items compiled from the Development (Design Repository) environment.

Upgrading the production environment involves these tasks:

  1. Additive Schema Changes. This step is optional and is run in the production environment. You can run this mode of the Database Configuration Utilities without taking the database offline. This mode makes schema changes that don't affect the operation of the application. This reduces the amount of time the production database must be offline to perform the upgrade. Testing Additive Schema Changes is also included in the process checklist for tuning the upgrade. This lets you verify Additive Schema Changes in the test environment before running it in the production environment.
  2. Prepare application data. These tasks are about preparing application data in the production database for migration.
  3. Upgrade database (upgrep). In the test environment, you start the Database Configuration Utilities in upgrep mode, and enter configuration information for the production environment. This includes an ODBC definition for connecting to the production Siebel database.

    This step causes the wizard to use the SQL for upgrading the test database to upgrade the production database.

  4. Full Migration. A one-time Full Migration is mandatory after upgrading your production Runtime Repository (RR) environment from any pre-Siebel CRM 2017 version. This ensures that the RR environment will know which Development (Design Repository) environment provided its repository. It also lets it accurately generate watermarks for future incremental migrations, as well as sync all administrative data (such as LOVs).

The SQL generated for the test database upgrade is preserved, and no new SQL is generated. This SQL has been tuned using the Upgrade Tuner and has been revised by the Prepare for Production mode.

You don't have to run the Database Configuration Utilities in upgphys mode. The upgphys steps are included in the production environment upgrep.