Siebel Database Upgrade Guide for DB2 UDB for z/OS > How the Siebel Database Upgrade Works >

About the Override File

Upgrades: Releases 6.x, 7.0.x, 7.5.x.

Environments: Development environment only.

The override.inp file allows you to override your existing database storage layout when you upgrade to Release 8.0.

Since Release 7.7, the Siebel database schema structure has the following characteristics:

• One table in each table space
• One table space in each database

This layout is referred to as the 1:1:1 model. See Planning Changes to the Physical Layout of the Schema for further information.

If you are upgrading from a pre 7.7 release of Siebel applications, you may want to switch to the 1:1:1 model from your existing database schema structure because it is more efficient. There are three options available when upgrading to the current release:

• Preserve the existing model of multiple tables in each table space and only build new tables with the 1:1:1 model.

  To use this option, extract a storage control file and merge it with an existing template. All existing definitions are preserved and new tables are built according to the definitions supplied in the template storage control file.

• Preserve the existing model for most tables but indicate that specific tables are to use the 1:1:1 model by adding the table names to the override.inp file. By default, the override.inp file has two table entries:
  • S_DOCK_TXN_LOG
  • S_SERVICE_SCRPT

    The existing definition for these two tables is not preserved during the upgrade. Therefore, these two tables can be built using the new model as specified in the template.

• Move all tables from the current model to the 1:1:1 model.

  To use this option, do not use the extract and merge process to create the storage control file. Instead, use the preconfigured storage control file. In the preconfigured storage control file, all tables are created using the 1:1:1 model. Therefore, each table is created in its own database or table space.

  The use of the preconfigured storage control file allows you to use the 1:1:1 model for all tables other than obsolete tables and customer extended tables. The preconfigured storage control file does not apply to obsolete or customer extended tables so there are no entries for them. You cannot put these into the override.inp file since there is nothing to override and the tables are not in the storage control file. In this case, the existing schema is preserved.

  The table spaces are not cleaned up unless they are empty. Some of the obsolete and customer extended tables are still in those table spaces so the upgrade process cannot just do a general cleanup.