Siebel Database Upgrade Guide > Postupgrade Tasks for the Siebel Database and File System >

Reapplying Schema Customizations in the Siebel Database

Upgrades from: All Supported Siebel releases.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

In the current release, tables are obsolete or have been replaced by new tables. If you added extension columns or foreign key (FK) columns to tables that are obsolete in the current release, you must reapply these changes to the new tables.

Reviewing Obsolete Tables

The upgrade process generates a report that you can review for information about tables that are either obsolete. This report, xtndobstbl.txt, lists the following:

• Custom columns in obsolete tables
• Custom foreign key columns pointing to obsolete tables
• EIM mappings for custom foreign key columns to access-control related obsolete tables
• Workflow columns by custom foreign key to obsolete tables
• Customer denormalized columns on obsolete tables
• Obsolete tables in the current release.

Each obsolete table is listed with one of three codes:

• Not Used. These tables are not used in the current release, but you may continue to use them. These tables are supported as is (for instance, with docking or EIM).
• EOL (end of life). These tables are not used in the current release, and they are not supported in future releases.
• Inactive. These tables have been discontinued, and are not supported in the current release. You must move extension columns and foreign key columns that reside on inactive tables to alternate tables.

If no tables are listed in xtndobstbl.txt, no action is required.

If this file lists any tables, reapply their custom extensions and foreign key columns to tables in the current release using Siebel Tools. See Configuring Siebel Business Applications.