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

Preparing the Development Environment Repositories for Upgrade

Upgrades: All upgrades.

Environments: Development environment only.

Four separate repositories are used during the development upgrade process.

Your existing development repository. To prevent a naming conflict, before you run the upgrade, rename your existing development repository (Siebel Repository) to Prior Customer Repository. After the upgrade, your new Release 7.7 development repository is given the name Siebel Repository.

Three new repositories. These are automatically loaded when you run the Siebel Upgrade Wizard:

• Prior standard repository
• New standard repository (Release 7.7)
• New customer repository (Release 7.7) which, after the merge, becomes the customized 7.7 repository.

Before these repositories are loaded, verify that your existing repositories do not use the names reserved for the upgrade process:

• New Customer Repository. Your new custom repository, which results from the merge, and includes your custom configurations.
• New Siebel Repository. The new Siebel standard repository.
• Prior vX.x Siebel Repository. The prior Siebel Repository.

To avoid running out of space when importing these repositories, make sure you correctly size your tables. The following tables have a high number of inserts during imprep:

• S_APPLET
• S_APPLET_INTL
• S_APPLET_METH_MI
• S_APPL_WEB_TMPL
• S_APPL_WTMPL_IT
• S_BOCOMP
• S_BUSCOMP_UPROP
• S_COLUMN
• S_CONTROL_INTL
• S_CONTROL_UPROP
• S_DDOWN_OBJECT
• S_EIM_FK_MAPCOL
• S_FIELD
• S_INDEX
• S_INDEX_COLUMN
• S_INTFLD_UPROP
• S_INT_CKEY_FLD
• S_INT_COMP
• S_INT_FIELD
• S_JOIN
• S_JOIN_SPEC
• S_LIST
• S_LIST_COLUMN
• S_PICKMAP
• S_SCREEN_VIEW
• S_UK_ATTJOIN
• S_LIST_COL_INTL
• S_USER_KEY_ATT
• S_VIEW_WTMPL_IT
• S_CONTROL
• S_EIM_ATT_MAP

Use the version of Siebel Tools that matches your old version of Siebel eBusiness applications (for example, Siebel Tools Release 6.x for upgrades from Release 6.x). Connect directly to the development Siebel Database Server, and then perform the following steps to make sure that your existing repositories follow the correct naming conventions:

To rename the repository

1. Using the appropriate prior version of Siebel Tools, connect to the Siebel Database Server.
2. Change the name of the existing repository, as described below:
   1. In the Object Explorer, click the Types tab.
   2. Click Repository.
   3. In the Repository view, click Name.
   4. Locate the appropriate repository in the list applet and rename it Prior Customer Repository.
3. Step off the list to commit the record to the database.

   NOTE:  The upgrade process verifies the repository names. If no repository is named Prior Customer Repository, the Siebel Repository is renamed to Prior Customer Repository in the target database so that the upgrade executes properly.

If you need more information about renaming repositories, refer to Configuring Siebel eBusiness Applications.