1. Database Upgrade Guide for DB2 for z/OS
  2. Required Tasks before Creating the Staging Database

Required Tasks before Creating the Staging Database

Before you create the staging database, use the Siebel source (old) release to complete these tasks:

Upgrades: All upgrades

Environments: All environments

  1. Select a schema owner for the staging database. Make sure the staging schema owner doesn't own any objects within the staging DB2 subsystem. The staging schema owner can be the same as the target schema owner.

  2. Do the following:

    1. Make sure you have a valid storage control file for the database to be upgraded. This contains the storage definitions of the existing database and is used to generate the DDL to build the staging database schema.

    2. Name this storage control file storage_target_extonly.ctl.

      If you don't have a valid storage control file, create one by running the Database Configuration Wizard and selecting the Extract from Catalog option. Specify database details for your existing Siebel database (the database to be upgraded). For more information on this task, see the Implementing Siebel Business Applications on DB2 for z/OS guide.

      The Extract from Catalog option extracts the storage layout of the database you specify from the DB2 catalog and creates a new storage control file that contains a copy of the storage definitions of the database.

  3. Make sure the logical repository definitions and the physical schema definitions of the database to be upgraded match by running the Database Configuration Wizard, and specifying the following options:

    • Siebel Database Operation: Run Database Utilities.

    • Database Utility Selection: Synchronize Schema Definition.

    • Repository Synchronization Mechanism: Generate DDL into Files.

    • Storage Control File: Specify the file you extracted in the previous step.

  4. Depending on the outcome of the synchronization process, do one of the following:

    • If the logical and physical schema database definitions match, no DDL is generated in the schema.sql file from the Synchronize Schema Definition process and no further action is required.

    • If the logical and physical schema database definitions do not match, the synchronization log file indicates the specific actions that are required to synchronize the schema definitions, such as rebuild tables, and the synchronization process generates the DDL required to perform the actions. Proceed to step 5.

  5. Click Yes to exit the Wizard, then do this:

    1. Navigate to the directory you assigned as the Output Directory.

    2. Transfer the schema.sql file to the z/OS host and ask your DBA to apply the DDL contained in the file.

For detailed information on running the Synchronize Schema Definition process, see see the Implementing Siebel Business Applications on DB2 for z/OS guide.