Siebel Database Upgrade Guide for DB2 UDB for z/OS > Performing Post-Upgrade Tasks On the Target Database >

Migrating Custom Business Component Configurations

Upgrades: Release 6.2.1 of Siebel Financial Services applications.

Environments: Development environment only.

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

Customized business component configurations (buscomps) which are based on customer extension columns or on Siebel columns in obsolete tables need to be identified and manually fixed after the upgrade. Siebel columns in obsolete tables are reconfigured and migrated during the upgrade. However, customer business components or custom extension columns on obsolete tables need to be migrated manually.

NOTE:  Custom extension columns on tables that are upgraded (not obsolete) are retained during the upgrade.

To review a list of the business components that require manual migration, review the upgcust.log file, located in the SIEBSRVR/log directory.

Critical obsolete tables are listed in Table 19.

The access control business component migration utility is run on the Prior Customer Repository by the Siebel Upgrade Wizard during upgrade of the Siebel database schema.

Several fields, business components, and columns may need to be reevaluated and recreated after your upgrade. A sample conversion script is available for migration of data to the new columns during the development upgrade.