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

About the Siebel Database 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. During this phase, your customizations are merged with the new Siebel release. A merged repository file and database schema file are created and become inputs to the production test 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 production test environment and production environment.

Flow of the Upgrade Within an Environment

The basic flow of the upgrade process is shown in Figure 1.

NOTE:  In production test environment and production environment upgrades, the upgrep + upgphys steps are run together and 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. For information on how to upgrade the infrastructure, see the Siebel Installation Guide for the operating system you are using.

Perform Preupgrade Tasks

This phase prepares the Siebel database for upgrade and includes such tasks as closing database connections, clearing pending workflow tasks, disabling customized triggers and editing and validating the storage control file.

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). Run the Database Configuration Wizard in upgrep mode, selecting the zSeries Staging of Files for Upgrade option. This generates the files required to build the staging database and generate the upgrade files required to perform the in-place upgrade of the database.
• Perform the in-place upgrade of the database. During this phase, a basic upgrade of the Siebel database schema is performed and repositories are loaded to prepare for the repository merge.

  The upgrep 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 Prior vx.x Siebel 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
• 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.
• Run postmerge utilities. You use Siebel Tools to run a set of utilities that examine the merged repository. The utilities analyze your customizations and apply changes to them as needed to conform to the user interface in the new release.
• Upgrade database (upgphys). You run the Database Configuration Wizard in upgphys mode. It further upgrades the Siebel database with changes resulting from the repository merge and completes the database upgrade.

  The Database Configuration Wizard also generates the customer repository definition file and logical schema definition file that are used as input to the production test environment and production upgrades.

  Specifically, this mode performs the following tasks:

  • Synchronizes the Siebel database schema to the logical schema definition in the merged repository.

    NOTE:  During the synchronization process, custom columns in the Siebel Schema that are not in the Siebel Repository are not removed but custom indexes in the Siebel Schema that are not in the Siebel Repository are removed.

  • Deduplicates intersection tables
  • Exports repository object definitions to a file, custrep.dat, and exports the logical schema definition to a file, schema.ddl

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

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

Perform Upgrade Tasks (Production Test Environment)

This phase upgrades a production test environment Siebel database to the new release allowing you to test how customizations work with the new release and to tune the upgrade scripts.

CAUTION:  You are required to contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services for help with tuning your upgrade scripts. If you do not, you may invalidate your support agreement.

This phase includes the following tasks:

• Prepare application data. These tasks are about preparing application data for migration.
• Prepare for Production Upgrade. Run the Database Configuration Wizard in Prepare for Production Upgrade mode. This mode does the following in the production test environment.

  NOTE:  You must define an ODBC connection to the development environment database before performing this upgrade step.

  • Examines the upgraded development environment database and generates SQL (dedup.jcl and dedup_prod.jcl files) that removes duplicate records from the intersection tables and sets up support for database aggregation.

    You only have to run the utility in Prepare for Production Upgrade mode once—either in a production test environment or in the live production environment— to generate the dedup.jcl and dedup_prod.jcl files.

  • Compares the repository schema and the physical database schema. Generates a file, SCINDX.SQL, which is used to remove obsolete indexes. SCINDX.SQL lists indexes present in the physical schema that are not present in the repository schema.
• Upgrade database (upgrep + upgphys). Run the Database Configuration Wizard in upgrep + upgphys mode, selecting the zSeries Staging of Files for Upgrade option. This generates the files required to build the staging database and generate the upgrade files required to perform the in-place upgrade of the database. The additive and non-additive schema upgrade files are generated separately.
• (Optional) Apply the additive upgrade files to upgrade the database. This is a non-disruptive upgrade process.
• Perform the in-place upgrade of the database. The following changes are made during this phase of the upgrade process:
  • 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
  • Makes several administrative changes to table data, including updating the schema version in S_APP_VER.
• Upgrade the repository and import seed data (upgrep + upgphys). Run the Database Configuration Wizard in upgrep + upgphys mode again, selecting the zSeries Seed/Repository Upgrade option to complete upgrade processing.
• Tune upgrade scripts (optional). You can improve the performance of the production environment upgrade by tuning the production upgrade scripts in the test environment.

  Run several production upgrades against the test database. This allows you to understand the upgrade process before performing the production upgrade, to conduct performance testing, and to fine-tune the upgrade scripts. After carrying out thorough performance testing, you can perform the live production upgrade using the tuned upgrade files.

Perform Upgrade Tasks (Production Environment)

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

• Prepare Application Data. These tasks involve preparing application data in the production database for migration.
• Upgrade database (upgrep + upgphys). Run the Database Configuration Wizard in upgrep + upgphys mode, selecting the zSeries Staging of Files for Upgrade option. This generates the files required to build the staging database and generate the upgrade files required to perform the in-place upgrade of the database. The additive and non-additive schema upgrade files are generated separately.

  NOTE:  If you have tuned the upgrade scripts during a production test upgrade and want to use them during your production upgrade, you do not have to perform this step. Instead, change the production test environment values in the upgrade files to production environment values and then apply these files on the Z/OS host to upgrade the target database. For further information on this task, see Process of Upgrading a Siebel Production Environment.

• (Optional) Apply the additive upgrade files to upgrade the database. This is a non-disruptive upgrade process.
• Perform the in-place upgrade of the database. The same changes are made during the in-place upgrade of the production environment as were made during the in-place upgrade of the production test environment.
• Upgrade the repository and import seed data (upgrep + upgphys). Run the Database Configuration Wizard in upgrep + upgphys mode again, selecting the zSeries Seed/Repository Upgrade option to complete upgrade processing.

NOTE:  You do not have to run the utility in Prepare for Production mode before starting your production environment upgrade. You ran it as part of the production test environment upgrade. The required upgrade SQL commands have already been generated.

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.

Related Topics

About the Siebel Upgrade Wizard and Driver Files

About the Siebel Database Configuration Utilities