Siebel Database Upgrade Guide for DB2 UDB for z/OS > How the Siebel Database Upgrade Works >

About the Database Configuration Wizard

Upgrades: All upgrades.

Environments: All environments.

The Database Configuration Wizard is part of the Siebel Configuration Wizard. It interactively gathers the information required to perform the following operations:

• Install the Siebel database. This wizard sets up the Siebel database in the RDBMS as part of a first-time installation of Siebel applications. It is also used to add a language to the Siebel Database Server installation.
• Upgrade the Siebel database. This wizard upgrades the Siebel database to a new release in a development or production environment.
• Import or export a Siebel repository. This wizard moves entire repositories between database environments with the same schema definition.
• Migrate a Siebel repository. This wizard migrates repositories between databases and synchronizes the target database schema with the migrated repository schema definition.
• Run database utilities. This group of wizards perform the following functions:
  • Synchronize a database schema with the Siebel Repository schema definition.
  • Convert existing Lists of Values (LOVs) to Multilingual Lists of Values (MLOVs).
  • Configure the database by extracting storage control files from the DB2 catalog and validating the extracted files.
  • Migrate the database from an EBCDIC or ASCII encoding format to a Unicode encoding format.

About Running the Upgrade Database Option

When you run the Upgrade Database option on the Database Configuration Wizard, the wizard prompts you for the upgrade environment (development or production) and the upgrade phase (upgrep, upgphys, or Prepare for Production Upgrade). The Wizard then prompts you for the information it needs about the upgrade environment to perform the upgrade.

After collecting and confirming the information, the wizard creates an upgrade configuration file and calls a driver that uses the environment information to create the SQL files required to upgrade your database.

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

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

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

Figure 2. Upgrade Flow

How the Upgrade Configuration File and SQL Files Are Created

When you run the Database Configuration Wizard, it does the following:

• Collects configuration information.
• Creates a master upgrade configuration file (UCF). This file maps the information you entered in the Database Configuration Wizard to environment variables. When the Siebel Upgrade Wizard is performing the steps in a driver file, it uses these variables to generate the command contained in each step.
• Prompts you to start the Siebel Upgrade Wizard. The wizard forwards the information in the UCF file to an SQL generator that creates or populates SQL files on the midtier with the required commands to perform the upgrade. You then transfer these files to the z/OS host and apply them.

  In some cases, you will need to modify the generated SQL files as required by Siebel Release Notes, Technical Notes, or Siebel Alerts before you transfer the files to the z/OS host.

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_MasterFileType.ucf

where:

• UPGRADEOPTION = the upgrade process you are performing. This can be one of the following:
  • Siebel database schema upgrade = upgrep
  • Custom database schema upgrade = upgphys
  • Siebel Database Upgrade (production) = upgrep + upgphys
  • Prepare for production upgrade = prepare_for_production_upgrade
• ENVIRONMENT = the environment that you are upgrading. This can be one of the following:
  • Development environment upgrades = dev
  • Production environment upgrades = prod
• VERSION = the version from which you are upgrading. The following numbers are used for the Siebel Release version of the file name:
  • 621
  • 704
  • 752
  • 752_200
  • 753
  • 77
  • 782
• MasterFileType = the type of master file. This can be one of the following:
  • Configuration files generated for the manual phase of the upgrep process (zSeries Staging of Files for Upgrade process) = mf_m
  • Configuration files generated for the automatic phase of the upgrep process (zSeries Seed/Repository Upgrade process) and for the upgphys process = mf

    The automatic phases of the upgrade process are run after the manual phases are completed.

Example

If you are upgrading from Siebel 7.0.4, the UCF files generated from the development environment upgrade are as follows:

master_upgrep_dev_704_mf_m.ucf

master_upgrep_dev_704_mf.ucf

master_upgphys_dev_704_mf.ucf

The UCF file generated from the Prepare for Production Upgrade mode is as follows:

master_prepare_for_production_upgrade.ucf