Renaming the Production Environment Repository

Upgrades: All upgrades.

Environments: Production test, production.

This topic is part of an upgrade process. See Performing a Siebel Database Upgrade.

Two separate repositories are used during the production upgrade process:

• Your existing production repository

• New Customer Repository

The New Customer Repository is loaded when you run the Siebel Upgrade Wizard.

To prevent a naming conflict, before you take your production database offline to run the in-place target database upgrade, rename your existing production repository (Siebel Repository) to Prior Customer Repository. After the upgrade, your new Siebel CRM production repository is given the name Siebel Repository.

Rename your existing production repository using the procedure described in the chapter in Siebel Database Upgrade Guide that describes how to upgrade the Siebel database.

Caution: Your upgrade will encounter errors if you have more than one existing repository for a production upgrade. Export, archive, and delete from the Siebel schema to be upgraded any redundant repositories before you upgrade your production environment.

For further information about renaming repositories, see Configuring Siebel Business Applications.