Bookshelf v7.7: About the Upgrade Process

Bookshelf Home | Contents | Index | PDF

Upgrade Guide for DB2 UDB for z/OS and OS/390 > How the Upgrade Works >

About the Upgrade Process

Upgrades: All upgrades.

Environments: All environments.

Upgrading to a new release involves two aspects:

The order in which to upgrade your environments
The flow of the upgrade process within each environment

Environment Upgrade Order

If you have a development environment, you must upgrade it first. This merges your customizations with the new release. A merged repository file and database schema file are created and become inputs to the development environment upgrade and production upgrade.

If you do not have a development environment or have not customized your repository, no repository merge is required. You can use the repository and schema definition files included in the new release to upgrade your development environment and production environment.

Flow of the Upgrade Within an Environment

The basic flow of the upgrade process is shown in Figure 1. This flow applies to development and production environment upgrades. However, when upgrading a production environment, there are several additional deployment steps.

Figure 1. Flow of the Upgrade Process

Upgrade the Infrastructure

The first phase is to upgrade your hardware and software to meet system and implementation requirements, which includes upgrading the Siebel Enterprise to the new release. This action upgrades the Siebel Servers and provides the programs, scripts, input files, and other files required to merge the repository and upgrade the Siebel database.

Perform Preupgrade Tasks

This phase prepares the Siebel Database for upgrade and includes such tasks as closing database connections, clearing pending workflow tasks, and disabling customized triggers.

Perform Upgrade Tasks (Development Environment)

This phase merges your customizations into the new release. This phase also upgrades the development environment database and includes these tasks:

Prepare application data. These tasks prepare test data for migration.
Upgrade database (upgrep). You run the Database Server Configuration utility in upgrep mode. This utility performs a basic upgrade of the Siebel Database schema and loads repositories to prepare for the repository merge.
Merge repository. You use Siebel Tools to merge your existing repository with the repository in the new release. Postmerge utilities upgrade form applets and verify that applets and views are configured correctly.
Upgrade database (upgphys). You run the Database Server Configuration utility in upgphys mode. It further upgrades the Siebel Database with changes resulting from the repository merge and completes the database upgrade.
The Database Server Configuration utility also generates the customer repository definition file and logical schema definition file that are used as input to the development environment and production upgrades.

Perform Upgrade Tasks (Production Environments)

This phase upgrades a production environment Siebel Database to the new release and includes the following tasks:

Prepare Application Data. These tasks are about preparing application data for migration.
Upgrade database (upgrep + upgphys). You run the Database Server Configuration utility in upgrep + upgphys mode. It performs a basic upgrade of the Siebel Database schema by importing the repository and schema definition files from the development environment upgrade and using these files to upgrade the Siebel Database and perform miscellaneous administrative tasks.

Perform Postupgrade Tasks

This phase is where you set up the environment, configure applications, and test the system as follows:

Set Up the Environment. These tasks set up the postupgrade environment, which includes extracting the developers' databases and running database statistics.
Application Administration. These tasks set up applications and include such things as setting up user access and visibility of views and screens.
Application Configuration. These tasks prepare applications for testing, including data migration for specific applications.
Test the System. These tasks test the system. For development environment upgrades, you perform basic unit tests to verify application function followed by a full suite of regression and stress tests to verify the system is ready for production.