Siebel Database Upgrade Guide for DB2 for z/OS > Basic Database Preparations for a Siebel Upgrade > Preparing the Storage Layout of the Schema >

About Extracting the Storage Control File

The information in your storage control file comes from the target database, that is, the database to be upgraded. When you extract the storage control file, you can choose one of two methods:

• Extract from Catalog. This method extracts the storage layout of your existing database from the DB2 catalog; the output is a new storage layout.

  Use this option when creating the storage control file that is used to generate the DDL to build the staging database schema. For information on this task, see Required Tasks before Creating the Staging Database.

  The Extract from Catalog method can also be used to perfect your target database layout by performing a dummy installation, manipulating the schema layout through native utilities, then extracting the customized layout. For information on the Extract from Catalog option, see Implementing Siebel Business Applications on DB2 for z/OS.

• Extract from Catalog and Merge with Template. This method preserves your existing layout. This method merges storage layout information from your existing database with information that you already entered into a storage template file provided with Siebel Business Applications. This preserves your prior layout, and your output is the prior physical layout merged with an 8.1 storage layout template.

  After you have created the staging database, use the Extract from Catalog and Merge with Template option to extract the storage layout of the Siebel staging database from the DB2 catalog and merge it with a Siebel CRM 8.1 storage control file so as to preserve any customizations you have made to the database layout in the upgraded database. For information on this task, see Required Tasks for Generating the Upgrade Files.

  The following list details scenarios that might occur during the extract and merge process and the behavior you can expect in these cases:

  • A database object exists in the existing database but not in the template. The definition of the database object is output to the new storage control file.
  • A database object is specified only in the template file. The definition of the database object is output to the new storage control file.
  • A database object is specified in both the existing database and the template. The layout of the existing database is extracted as the default. However, you can manually override this behavior by creating a file called override.inp in the BIN directory under SIEBEL_ROOT. Place any tables that you want to override into this file.

Related Topic

Preparing the Storage Layout of the Schema