Bookshelf Home | Contents | Index | PDF     

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

Reapplying Schema Customizations in the Siebel Database

Upgrades from: All 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.

Obsolete Tables That Cannot Be Used

Table 58 lists examples of previously used tables that are inactive in Siebel 7.7.x (you can no longer use these tables) and lists the suggested new tables to which you need to reapply custom extensions. 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 Oracle's Siebel Technical Support to validate the reapplication of extension columns and to review the steps necessary to migrate any extension column data to the new tables.

Table 58. Examples of Tables That Are Obsolete in Siebel 7.7.x
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 created many custom extension columns on the tables S_EMPLOYEE or S_ORG_INT, both of which are no longer used in Siebel 7.7.x, the joins between the tables are not accurate. This may result in SQL errors when you launch the Siebel client.

In such cases, using Siebel Tools, you must 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 must then review the business component configuration to make sure that the client operates properly. You may need to do this in one of the following cases:

  • 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

Obsolete Tables You Can Continue To Use

Table 59 lists examples of previously used tables that are obsolete in Siebel 7.7.x, but that you can continue to use.

Table 59. Examples of Tables That Are Not Used in Siebel 7.7.x
Previous Table
Suggested New Table

S_CRSE

S_SRC, S_SRC_EVT (class records)

S_PROD_INT, S_PROD_INT_CRSE (course records)

S_CRSE_OFFR

S_SRC, S_SRC_EVT

S_CRSE_REG

S_SRC_EVT_REG

S_CTLG_CAT_REL

S_CTLG_CAT

S_DNB_CONTACT

S_PRSP_CONTACT

S_OPTY_PROD

S_REVN

S_TMSHT_LINE

S_TMSHT_ITEM, S_TMSHT_LN

Obsolete Tables that Are Now Active

Table 60 lists examples of tables that were unused in previous releases of Siebel Business Applications, but are now used in Siebel 7.7.x.

Table 60. Examples of Previously Unused Tables That Are Used in Siebel 7.7.x
Siebel 7.x Name
Former Name

S_ACT_EMP

S_EVT_ACT

S_ACT_CON

S_EVT_ACT

Opportunity Product Migration

At Siebel 7.7, data is migrated from S_OPTY_PROD to S_REVN. As a result, if you have custom objects that point to S_OPTY_PROD, you must remap the affected base or extension tables. You may have to remap extension columns pointing to S_OPTY_PROD as well.

The following base or extension tables are affected in the migration from S_OPTY_PROD to S_REVN:

  • S_FN_OFFR_COLT
  • S_OPTY_PROD1_FNX
  • S_FN_OFFR_FEE
  • S_OPTY_PROD_FNX
  • S_FN_OFFR_SCHD
  • S_OPTY_PROD_FNXM
  • S_OPTYPRD_ORG

 

For example, if a child object pointed to S_OPTY_PROD, you must manually remap the object to S_REVN.

    
Siebel Database Upgrade Guide