Upgrade Guide for DB2 UDB for z/OS > Postupgrade Tasks for a Development Environment >

Reapplying Custom Columns to the Siebel Database

Upgrades: All upgrades.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

Several tables used in prior versions of Siebel Business applications are no longer used, or have been replaced by new tables, in the current release. If you added extension columns or foreign key (FK) columns to tables that are obsolete in the current release, you may want to reapply these changes to the new tables that have replaced them.

The upgrade process generates a report that you can review for information about obsolete tables that will help you decide whether or not you need to reapply schema customizations. This report, xtndobstbl.txt, lists the following:

• Obsolete tables in the current release
• Custom columns in obsolete tables
• Custom foreign key columns pointing to obsolete tables
• EIM mappings for custom foreign key columns to obsolete tables
• Workflow columns by custom foreign key to obsolete tables
• Custom denormalized columns to Siebel base tables that might be obsolete

Each obsolete table is listed with one of three status codes:

• Not Used. These tables are not used in the current release but you can continue to use them; for example, S_ORG_PROD or S_PERIOD BU. 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 it is recommended that you delete them because they will not be supported in future releases; for example, old S_*_IF tables.
• Inactive. These tables have been discontinued, and are not supported in the current release. Extension columns that reside on inactive tables must be moved to alternate tables; for example, S_EMPLOYEE should be moved to S_CONTACT, S_USER, or S_EMP_PER.

If no tables are listed in xtndobstbl.txt, no action is required. If this file lists any tables, you can reapply their custom extensions and foreign key columns to tables in the current release using Siebel Tools. For further information on this task, see Configuring Siebel Business Applications.

Table 35 lists examples of previously used tables which are inactive in Release 7 (you can no longer use these tables) and lists the suggested new tables to which custom extensions need to be reapplied. The new tables are recommendations only; the tables that you need to apply the extensions to might vary depending on their type and use. Contact Siebel Technical Services to validate the reapplication of extension columns and to review the steps necessary to migrate any extension column data to the new tables.

This data must be migrated during both the development and production environment upgrades.

If you have created many custom extension columns on the tables S_EMPLOYEE or S_ORG_INT, both of which are no longer used in Release 7, the joins between the tables will not be accurate. This may result in SQL errors when you launch the Siebel client.

In such cases, using Siebel Tools, you need to manually create corresponding extension columns in the new target tables, and manually move the data to the new extension column on the new table before you continue migration of the application. You should then review the business component configuration to make sure that the client will operate properly.

You may need to do this in one of the following instances:

• Fields based on custom extension columns in S_EMPLOYEE or S_ORG_EXT
• Fields based on custom extension tables from S_EMPLOYEE or S_ORG_INT with or without join
• Custom joins to custom extension tables from S_EMPLOYEE or S_ORG_INT

If you review the xtndobstbl.txt file after you run the buscomp migration utility, you will find a list of fields that require your attention.

Table 36 lists examples of previously used tables that are no longer used in Release 7, but that you may want to continue to use.

Table 37 lists examples of tables which were unused in previous releases of Siebel Business applications, but are now used in Release 7.