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

Preparing Production Environment Repositories for Upgrade

Upgrades: All upgrades.

Environments: Production environment only.

Two separate repositories are used during the production upgrade process:

• Your existing production repository. To prevent a naming conflict, before you run the upgrade, rename your existing production repository (Siebel Repository) to Prior Customer Repository. After the upgrade, your new Release 7 production repository will be given the name Siebel Repository.
• New Customer Repository. This repository will be loaded when you run the Siebel Upgrade Wizard.

CAUTION:  Your upgrade will encounter errors if you have more than one existing repository for a production upgrade. Export and archive any redundant repositories from your environment before you upgrade your production environment.

Renaming Your Existing Production Repository

You must rename your existing production repository so that it is recognized by the upgrade process.

To rename your existing production repository

1. Use the version of Siebel Tools that matches your prior version of Siebel eBusiness applications (for example, Siebel Tools Release 6.x for upgrades from Release 6.x) to connect to the Siebel Database Server.
2. Change the name of the existing repository:
   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.

      TIP:   Differentiate this repository from your development environment Prior Customer Repository by adding a prefix to the name; for example, 20031202 Prod Prior v6.x Customer Repository.

3. Step off the list to commit the record to the database.

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

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