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
BINdirectory under SIEBEL_ROOT. Place any tables that you want to override into this file.