1. Database Upgrade Guide for DB2 for z/OS
  2. Extracting the Storage Control File

Extracting the Storage Control File

After you have created the staging database but before you begin to generate the upgrade files, you must extract the storage control file from the staging database and merge it with a Siebel CRM template. You do this using the Database Configuration Wizard Extract from Catalog and Merge with Template option. Depending on the type of upgrade you are performing, assign one of the following names to the extracted storage control file:

  • Development environment upgrade: storage_upg_dev.ctl

  • Production environment upgrade: storage_upg_prod.ctl.

This task is a step in Process of Preparing the Storage Layout of the Schema.

To extract the storage control file

  1. Run the Database Configuration Wizard.

    For information on running the Database Configuration Wizard, see About Running the Database Configuration Wizard on Windows or About Running the Database Configuration Wizard Under UNIX.

  2. Enter the information shown in Information Required for the Database Configuration Wizard Extract Option when prompted by the Database Configuration Wizard. Collect this information and verify it before running the utility.

  3. Save the information you have entered and launch the Upgrade Wizard as described in Running the Database Configuration Wizard

    The database catalog is read and your prior custom database layout is merged with one of the Siebel database layout templates for the current release (located in the DBSRVR_ROOT\db2390 directory). New objects take a layout from one of the layout templates. By default, new tables are created as one-table-per-database to prevent concurrency and locking errors.

    Note: If you choose a Siebel storage control file template that includes partitioning, and the existing database schema does not include partitioning, by default, the existing database objects are not partitioned in the storage control file generated (that is, the database catalog overrides the templates) unless you specify the table names in the override input file (override.inp).

    Before using the merged storage control file, you must verify it against the staging database. For information on this task, see Validating the Extracted Storage Control File.