Bookshelf Home | Contents | Index | PDF     

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

Job Flow of a Production Database Upgrade

Upgrades: All upgrades.

Environments: Production environment only. Does not apply to production test environment.

This topic describes the major steps in a production database upgrade using the Database Configuration Wizard and Upgrade Wizard. This topic does not describe all the pre and postupgrade tasks you must complete for a production environment. See Process of Upgrading a Siebel Production Environment for a description of all the steps in upgrading a production environment.

The production environment upgrade job flow differs from a development environment upgrade job flow primarily in that a repository merge is not required. The repository (custrep.dat) and the logical schema (schema.ddl) are exported from the upgraded development environment and used in the production upgrade.

A production database upgrade job flow, as illustrated in Figure 3, is largely the same as the job flow of the upgrep stage of a development database upgrade.

Figure 3. Flow of a Production Database Upgrade
Click for full size image

The main steps in the production upgrade illustrated in Figure 3 are as follows:

  1. Inputs to the Production Upgrade. The files required for the production upgrade are:
    • The storage control file (storage.ctl). This file specifies the storage layout of your upgraded database. Create and validate the storage.ctl before running a production upgrade.
    • The custrep.dat file (new customized repository) and the schema.ddl file (modified schema definition file). These files are generated during the development upgrade and must be copied to the appropriate upgrade directory before running a production upgrade.
  2. Prepare for Production (7.5.3 Upgrades only): Run the Database Configuration Wizard on the midtier in Prepare for Production Upgrade mode to generate dedup files; the dedup files remove duplicate records from the intersection tables.
  3. Run upgrep + upgphys. Run the Database Configuration Wizard on the midtier:
    1. Enter production environment information to create the production upgrade configuration file. Specify the following values:
      • Upgrade Option: Upgrade Siebel Database Schema (upgrep + upgphys)
      • Upgrade Process: zSeries Staging of Files for Upgrade
    2. Launch the Upgrade Wizard to generate the DDL files that will be used to build the staging database.

      The Wizard generates the staging database schema files on the midtier and then stops (Pause #0).

  4. Create the Staging Database. Transfer the staging DDL files from the midtier to the z/OS host and apply them. Create the staging database and prepare the z/OS host upgrade environment.
  5. Generate Additive Schema Upgrade Files. Restart the Database Configuration Wizard on the midtier. The wizard generates files and then stops at Pause #1.
  6. Apply Pause #1 Files. The files generated by the Upgrade Wizard on the midtier up to pause #1 consist of JCL and SQL templates and REXX execs that are run on the z/OS host against the staging database. These jobs are used to perform preupgrade tasks for the staging database. Do the following:
    1. FTP the files generated by the Upgrade Wizard from the midtier to the mainframe.
    2. Receive the files, unpack the staging data sets into PDS format, and create JCL members to run the additive schema and PRET jobs against the staging database.
    3. Apply additive schema changes to the staging database.
    4. Run PRET jobs against the staging database.
  7. Generate Nonadditive Schema Upgrade Files. Restart the Database Configuration Wizard on the midtier. The wizard generates files and then stops at Pause #2.
  8. Apply Pause # 2 Files. The files generated by the Upgrade Wizard on the midtier up to pause #2 include nonadditive schema files, load control cards and JCL templates, and unload SQL and JCL templates. Use the files generated up to this point to perform the in-place upgrade of the staging database. Do the following:
    1. FTP the files that have been generated from the midtier to the host.
    2. Modify the load and unload data sets.
    3. Run the unpack jobs to populate PDS members.
    4. Customize the UNLOAD and LOAD jobs for target tables with CLOB columns.
    5. Add jobcards and Siebel logging to the Load, Unload, and data migration jobs.
    6. Apply the nonadditive schema changes to the staging database.
    7. Create temporary tables and indexes for the data migration scripts.
    8. Generate index rebuilds.
  9. Generate the SCINDX Upgrade File. Restart the Database Configuration Wizard on the midtier. The wizard generates files and then stops at Pause #3.
  10. Apply Pause # 3 Files. The SCINDX file generated at this point is used to rebuild indexes. Do the following:
    1. FTP the SCINDX.SQL file from the midtier to the z/OS host.
    2. Apply the SCINDX.SQL file to rebuild indexes.

      This completes the file generation process

  11. Perform Pre-Upgrade Tasks for the Target Database as follows:
    1. On the z/OS host, build the JCL templates that will be used to perform the target database in-place upgrade by applying target database information to the JCL templates that were used to run the staging database in-place upgrade processes.
    2. Create and load Siebel log tables.
    3. (Optional) Apply additive schema changes.
  12. Perform the In-Place Upgrade of the Target Database as follows:
    1. Remove interface tables, triggers, and stored procedures from the database.
    2. Run PRET jobs to prepare the target database for table creation during the upgrade.
    3. Apply nonadditive schema changes to the target database.
    4. Create, bind, and test the stored procedures.
    5. Run the Data Migration jobs to migrate pre-8.1 Siebel data to version 8.1 data.

      There are optional data migration scripts for Household data and for Siebel Financial Services (FINS) applications.

    6. Remove old indexes, create new 8.1 indexes, and run index rebuild jobs.
  13. Upgrade the Repository and Import Seed Data as follows:
    1. Run the Database Configuration Wizard on the midtier.
    2. Enter production environment information to create the production upgrade configuration file. Specify the following values:
      • Upgrade Option: Upgrade Siebel Database Schema (upgrep + upgphys)
      • Upgrade Process: zSeries Seed / Repository Upgrade
    3. Launch the Upgrade Wizard. The Upgrade Wizard automatically runs the remaining DML upgrade jobs from the midtier to perform a number of tasks, including the following:
      • Deletes the old license key.
      • Verifies the repository name and imports the New Customer Repository from the upgraded development environment.
      • Upgrades seed data to the new version.

The production database upgrade is now completed.

    
Siebel Database Upgrade Guide for DB2 for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.