Upgrade Guide > How the Siebel Database Upgrade Works >

About the Siebel Database Server Configuration Utilities

Upgrades: All Siebel upgrades.

Environments: Development, production test, production.

The Database Server Configuration Utilities performs the upgrep and upgphys portion of an environment upgrade. You must also run the Database Server Configuration Utilities in Prepare for Production mode during the production test environment upgrade.

The Database Server Configuration Utilities requests information from you about the upgrade environment and creates an upgrade configuration file. It then calls a driver that uses the environment information to set up SQL scripts required to upgrade your database.

After you run the Database Server Configuration Utilities, you run the Upgrade Wizard. The Upgrade Wizard opens a driver file containing the steps for the upgrade and executes the steps.

To upgrade a development environment, production test environment, and production environment, you must run the Database Server Configuration Utilities (and Upgrade Wizard) several times, as shown in Table 9.

Figure 2 shows how the Database Server Configuration Utilities (and Upgrade Wizard) work together with the Siebel Tools repository merge to upgrade your environments.

Figure 2. Database Server Configuration Utilities and Siebel Tools Repository Merge

Development Environment Upgrades

For a development environment upgrade, you run the utility twice, once in each of the following modes:

• upgrep. This mode makes the following changes:
  • Drops interface tables and database triggers
  • Populates columns that must change from NULL to NOT NULL
  • Creates new tables. Merges existing tables.
  • Prepares for index creation. Verifies that there are no unique key violations.
  • Creates indexes
  • Imports seed data
  • Imports the version x.x Prior Customer Repository, New Siebel Repository, and New Customer Repository
  • Makes modifications to repository objects to prepare for the repository merge
  • Updates primary children foreign key references
  • Performs miscellaneous file actions
• upgphys. This mode makes the following changes:
  • Synchronizes the Siebel Database schema to the logical schema definition in the merged repository
  • Deduplicates intersection tables
  • Exports repository object definitions to a file, custrep.dat
  • Exports the logical schema definition to a file, schema.ddl

    These two files are used as input to the production test environment and production environment upgrades.

  • Renames the New Customer Repository to Siebel Repository
  • Updates the schema version in S_APP_VER

Production Test Environment Upgrades

For a production test environment upgrade, you run the utility three times:

• Prepare for Production. This mode does the following in the production test database:
  • Examines the development environment database and generates SQL that deduplicates intersection tables and sets up support for database aggregation.

    In the production test environment, you must define an ODBC connection to the development environment database before performing this upgrade step.

  • Compares the repository schema and the physical database schema. Generates a file that lists indexes present in the physical schema that are not present in the repository schema. You can decide whether to drop these indexes.
• upgrep. This mode makes the following changes:
  • Drops interface tables and database triggers
  • Populates columns that must change from NULL to NOT NULL
  • Uses the custrep.dat and schema.ddl files from the development environment upgrade to create new tables and merge existing tables
  • Prepares for index creation. Verifies that there are no unique key violations.
  • Creates indexes
  • Imports seed data
  • Updates primary children foreign key references
  • Performs miscellaneous file actions
• upgphys. This mode makes several administrative changes to table data, including updating the schema version in S_APP_VER. It does not make schema changes.

Production Environment Upgrades

After you have completed testing applications and have tuned the upgrade SQL commands, you perform the production upgrade.

The production upgrade uses the SQL commands generated in the production test environment. In the production test environment, you perform the following steps to upgrade your production environment Siebel Database:

• Define an ODBC connection to the production environment Siebel Database
• Prepare for Production. This step is not required. You ran it as part of the production test environment upgrade. The required changes have already been made to the upgrade SQL commands.
• upgrep. Run the Database Server Configuration Utilities. Enter information for the production environment (not the production test environment), including the new ODBC definition.

  The Database Server Configuration Utilities updates the upgrade configuration file with production environment information. A lock file that was set when you ran the utility previously, prevents new SQL from being generated. This preserves the SQL you have revised and tuned.

  When you run the Upgrade Wizard, it reads the production environment information from the configuration file and uses the production test environment SQL commands to upgrade the production environment Siebel Database.

  The upgrep step makes the same changes as when it ran in the production test environment.

• upgphys. Run the Database Server Configuration Utilities. Enter information for the production environment (not the production test environment), including the new ODBC definition.

  The Upgrade Wizard uses the upgrade SQL commands in the production test environment to upgrade the production environment Siebel Database.

  The upgphys step makes the same changes as when it ran in the production test environment.

How the Upgrade Configuration File and SQL Files Are Created

When you run the Database Server Configuration Utilities, it does the following:

• Collects configuration information
• Creates a driver upgrade configuration file (UCF). This file maps the information you entered in the Database Server Configuration Utilities to environment variables. When the Upgrade Wizard is performing the steps in a driver file, it uses these variables to execute the command contained in each step.
• Forwards the information to an SQL generator that creates or populates SQL files with the required commands. The SQL generator extracts these commands from an intermediate XML file containing all the SQL commands required for an upgrade.
• Prompts you to start the Upgrade Wizard.

  In some cases, you will need to modify the generated SQL files as required by Release Notes, Technical Notes, or Alerts before you run the Upgrade Wizard. To do this, answer No when prompted to run the Upgrade Wizard. Then, edit the SQL files and manually launch the Upgrade Wizard.

How to Locate Master Configuration Files

Master upgrade configuration files are stored in the following location:

Windows: SIEBEL_ROOT\bin

UNIX: $SIEBEL_ROOT/bin

Master upgrade configuration files use the following naming convention:

master_UPGRADEOPTION_ENVIRONMENT_VERSION.ucf

where:

• UPGRADEOPTION = the upgrade process you are performing
  • Siebel Database schema upgrade = upgrep
  • Custom database schema upgrade = upgphys
  • Prepare for production upgrade = prepare_for_production_upgrade
• ENVIRONMENT = the environment that you are upgrading
  • Development environment upgrades =dev
  • Production environment upgrades =prod
• VERSION = the version from which you are upgrading

For example, if you are upgrading from Siebel 7.0.4, the master configuration file generated from the development environment upgrep is as follows:

master_upgrep_dev_704.ucf

The master configuration file generated from the Prepare for Production mode is as follows:

master_prepare_for_production_upgrade.ucf

Related Topic

About the Siebel Upgrade Wizard and Driver Files