Upgrade Guide for DB2 UDB for z/OS > How the Upgrade Works >
About the Database Server Configuration Utility
Upgrades: All upgrades. Environments: All environments. The Database Server Configuration Utility performs the upgrep and upgphys portions of an environment upgrade. You must also run the Database Server Configuration Utility in Prepare for Production Upgrade mode before the production environment upgrade. The Database Server Configuration Utility 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 create the SQL scripts required to upgrade your database. After you run the Database Server Configuration Utility, 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 Server Configuration Utility (and Siebel Upgrade Wizard) several times, as shown in Table 9.
Table 9. Database Server Configuration Utility Modes
|
Select This Environment Type |
Select This Upgrade Option |
|
Development |
upgrep |
|
Development |
upgphys |
|
Production |
Prepare for Production Upgrade |
Prod. test env. upgrep + upgphys
|
Production |
upgrep + upgphys |
Production env. upgrep + upgphys
|
Production |
upgrep + upgphys |
Figure 2 shows how the Database Server Configuration Utility (and Siebel Upgrade Wizard) work together with the Siebel Tools repository merge to upgrade your environments.
Figure 2. Database Server Configuration Utility and Siebel Tools Repository Merge
|
How the Upgrade Configuration File and SQL Files Are Created
When you run the Database Server Configuration Utility, it does the following:
- Collects configuration information
- Creates a master upgrade configuration file (UCF). This file maps the information you entered in the Database Server Configuration Utility to environment variables. When the Siebel 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 Siebel Upgrade Wizard. The wizard uses the UCF file to execute the SQL files and other input files against the Siebel Database.
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 run the Siebel Upgrade Wizard. To do this, answer No when prompted to run the Siebel Upgrade Wizard. Then, edit the SQL files and manually launch the Siebel Upgrade Wizard. See Starting the Siebel Upgrade Wizard for more information. 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 UCF file generated from the development environment upgrep is as follows: master_upgrep_dev_704.ucf
The UCF file generated from the Prepare for Production Upgrade mode is as follows: master_prepare_for_production_upgrade.ucf
About Parameter Validation
The Database Server Configuration utility validates certain parameters, and does not proceed if you enter an invalid parameter. The configuration wizard validates the following information:
- That you have renamed the Siebel Repository to Prior Customer Repository
- That tablespaces exist in your database
- That username and password are valid
- That tableowner and tableowner password are valid
- That the language pack is installed
- That the directories chosen exist
|