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

Reapplying Custom Extensions and FK Columns on Obsolete Tables


Upgrades: All upgrades.

Environments: Development environment only.

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

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

The upgrade process generates a report that you can review for information about obsolete tables. This report, xtndobstbl.txt, lists custom columns in obsolete tables.

Several tables used in prior versions of Siebel eBusiness applications are no longer used, or have been replaced by new tables in Release 7. The new configuration uses the new tables. You need to reapply the extensions that you added to previous versions of the tables to the new tables.

The Database Server Configuration Wizard generated a report that you must review for information about tables that are either obsolete or no longer in use for Release 7. This report, xtndobstbl.txt, lists extension columns that reside on obsolete tables, and therefore need to be moved to alternate tables. Each table is listed with one of three status codes:

  • Not Used. These tables are not used in Release 7, 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 Release 7, and the recommendation is that you delete them since 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 Release 7. 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, their custom extensions must be reapplied to Siebel eBusiness applications Release 7 tables using Siebel Tools. See Using Siebel Tools.

Table 29 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.

Table 29. Examples of Tables That Are Obsolete in Release 7 
Previous Table
Suggested New Table

S_EMPLOYEE

S_CONTACT, S_USER, S_EMP_PER

S_EMP_POSTN

S_PARTY_PER

S_ORG_INT

S_ORG_EXT, S_BU

S_POSTN_RPT_REL

S_PARTY_RPT_REL

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 30 lists examples of previously used tables that are no longer used in Release 7, but that you may want to continue to use.

Table 30. Examples of Tables That Are Not Used in Release 7
Previous Table
Suggested New Table

S_CRSE

S_SRC, S_SRC_EVT

S_CRSE_OFFR

S_SRC, S_SRC_EVT

S_CRSE_REG

S_SRC_REG

S_CTLG_CAT_REL

S_CTLG_CAT

S_OPTY_PROD

S_REVN

S_TMSHT_LINE

S_TMSHT_ITEM, S_TMSHT_LN

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

Table 31. Examples of Previously Unused Tables That Are Used in Release 7
Now Used Table
Used to be...

S_ACT_EMP

S_EVT_ACT

S_ACT_CON

S_EVT_ACT

Upgrade Guide for DB2 UDB for z/OS and OS/390