Siebel Database Upgrade Guide for DB2 UDB 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 (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 as-is. The output is a new storage layout.

  NOTE:  This 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 merges storage layout information from your existing database with information that you already entered into a storage template file provided by Siebel. This preserves your prior layout, and your output is the prior physical layout merged with an 8.0 storage layout template.

  The first time that you run an upgrade, when you extract your storage control file, you must use the Extract from Catalog and Merge with Template option to preserve your existing layout. The list below details scenarios that may 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.

    CAUTION:  Partitioned tables were not supported for the 6.x releases. If you applied partitioning to release 6.x tables, carefully review the extracted data and modify it to conform with Siebel naming conventions as appropriate. If you have questions about amending the storage control file, create a service request (SR) on My Oracle Support.