Siebel Database Upgrade Guide for DB2 for z/OS > How the Siebel Database Upgrade Works >
About the Siebel Database Configuration Utilities and Database Configuration Wizard
Upgrades: All upgrades. Environments: All environments. The Database Configuration Utilities comprise a set of files that you install on a Siebel Server computer. These files are accessed when you run the Database Configuration Wizard and the Siebel Upgrade Wizard to install, configure, or upgrade the Siebel database on the DB2 host, or to perform other operations on the Siebel database after it is installed. You can use any upgraded Siebel Server to perform an upgrade of the Siebel database. For best performance, however, install the Siebel Database Configuration Utilities files on the Siebel Server that you will use to perform the upgrade. The Siebel Database Configuration Utilities files are installed at the same directory level as the Siebel Server in a directory called dbsrvr . For example, if the Siebel Server is installed in C: \sba81 \siebsrvr (Windows), then the Siebel Database Configuration Utilities are installed in C: \sba81 \dbsrvr . To edit and execute Siebel Database Configuration Utilities procedures and maintenance scripts, you must have READ-WRITE access to the Siebel Server bin directories in SIEBEL_ROOT (Windows), $SIEBEL_ROOT (UNIX). 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 Business 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 the Siebel 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 requires 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.
Table 5. Database Configuration Wizard Modes
|
Select This Environment Type |
Select This Upgrade Option(s) |
|
Development |
upgrep: zSeries Staging of Files for Upgrade |
|
Development |
upgrep: zSeries Seed/Repository Upgrade |
|
Development |
upgphys |
Production test environment
prepare for production (7.5.3 Upgrades only)
|
Production |
Prepare for Production Upgrade |
Production test environment
|
Production |
upgrep + upgphys: zSeries Staging of Files for Upgrade |
Production test environment
|
Production |
upgrep + upgphys: zSeries Seed/Repository Upgrade |
NOTE: If you have completed a production test upgrade and have tuned the SQL and JCL upgrade files on the z/OS host, you can use these files to perform the target database upgrade in the production environment. In this case, you do not have to run this upgrade step.
|
Production |
upgrep + upgphys: zSeries Staging of Files for Upgrade |
|
Production |
upgrep + upgphys: zSeries Seed/Repository Upgrade |
Figure 2 shows how the Database Configuration Wizard (and Siebel Upgrade Wizard) work together with the Siebel Tools repository merge to upgrade your environments. NOTE: The Prepare for Production step is required for upgrades from Siebel CRM version 7.5.3 only.
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 have to modify the generated SQL files as required by Alerts, Bulletins, or Siebel Release Notes on My Oracle Support 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: DBSRVR_ROOT \DB2390\upgrade \Version
UNIX: $DBSRVR_ROOT/ DB2390/upgrade /Version
where Version is the version from which you are upgrading Master upgrade configuration files use the following naming convention: master_ UPGRADEOPTION _ ENVIRONMENT _ VERSION_MasterFileType .ucf
where:
UPGRADEOPTION is the upgrade process you are performing. This can be one of the following:
upgrep. Siebel database schema upgrade.
upgphys. Custom database schema upgrade.
upgrep. Siebel Database Upgrade (production).
prepare_for_production_upgrade. Prepare for production upgrade; applies to 7.5.3 upgrades only.
ENVIRONMENT is the environment that you are upgrading. This can be one of the following:
- dev. Development environment upgrades.
- prod. Production environment upgrades.
VERSION is the version from which you are upgrading. The following numbers are used for the Siebel version of the filename:
MasterFileType is the type of master file. This can be one of the following:
Example
If you are upgrading from Siebel CRM version 7.5.3, the UCF files generated from the development environment upgrade are as follows: master_upgrep_dev_ 753_mf_m.ucf
master_upgrep_dev_ 753_mf.ucf
master_upgphys_dev_ 753_mf.ucf
The UCF file generated from the Prepare for Production Upgrade mode is as follows: master_prepare_for_production_upgrade.ucf
|