Upgrade Guide for DB2 UDB for z/OS and OS/390 > How the Upgrade Works >

About the Override File

Upgrades: All upgrades.

Environments: Development environment only.

There are three options when upgrading to the current release:

• Preserve the existing model of multiple tables per tablespace 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 source 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 of the source tables but specify specific source tables to use the 1:1:1 model.

  To use this option, use the override.inp file. By default, this file has two table entries:

  • S_DOCK_TXN_LOG
  • S_SERVICE_SCRPT

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

• Move all source 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 with the 1:1:1 paradigm. Therefore, each table is created in its own database or tablespace and the data is moved from the source to the target table.

  The use of the preconfigured storage control file allows you to have the 1:1:1 model for all tables except for 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 tablespaces are not cleaned up unless they are empty. Some of the obsolete and customer extended tables are still in those tablespaces so the upgrade process cannot just do a general cleanup.