Bookshelf Home | Contents | Index | Search | PDF

Upgrade Guide for Microsoft Windows > Preupgrade Tasks >

Preparing Production Environment Repositories

---

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.5 production repository is given the name Siebel Repository.
• New Customer Repository. This repository is loaded when you run the upgrade wizard.

Renaming Your Existing Production Repository

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 production 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 Siebel Tools Reference.

Bookshelf Home | Contents | Index | Search | PDF