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

Options for Extracting the Storage Control File

This topic describes the options available when you run the Database Configuration Wizard to extract the storage control file.

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

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
• Extract from Catalog and Merge with Template

Extract from Catalog

This method extracts the storage layout of your existing database from the DB2 catalog; the output is a representation of the existing target database objects.

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 a storage template file provided with Siebel Business Applications. This preserves your prior layout, and your output is the prior physical layout merged with a storage layout template for the current release.

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 storage control file for the current release 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.

Objects Extracted to the Storage Control File

When you select the Extract from Catalog and Merge with Template option, the extracted storage control file does not list all database objects in the Siebel schema. 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.

  NOTE:  Index objects are not output to the new storage control file if they are specified in both the existing database and the template and if there are no specific attribute differences between them. In this case, if you import the extracted storage control file into the Siebel Database Storage Configurator (dbconf.xls), the index objects are not displayed and their attributes cannot be edited.