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

Renaming the Siebel Repository Using Siebel Tools

Upgrades: All upgrades.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

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

Four separate repositories are used during the development upgrade process:

• Your existing development repository

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

• Three new repositories which are automatically loaded when you run the Siebel Upgrade Wizard.
  • Prior standard repository
  • New standard repository (Release 7.8)
  • New customer repository (Release 7.8) which, after the merge, becomes the customized 7.8 repository.

    Before these repositories are loaded, you must verify that your existing repositories do not use the names reserved for the upgrade process (see Step 7 below).

To rename the repository

1. Start Siebel Tools and connect to the Siebel Database.

   Use the version of Siebel Tools for the Siebel release from which you are upgrading.

2. If you archived repository objects as .sif files, and you want to have them available in your application, import these archive files back into the repository.

   If you do not check these objects back into the repository, they will not be upgraded. You need only to check in those archived objects that you need in the future and want to have available in your upgraded application.

3. Choose View > Options.
4. Click the Object Explorer tab.

   The Object Explorer hierarchy displays.

5. Locate Repository in the list, put a check mark in the adjacent box, and then click OK.

   This exposes the repositories.

6. In the Object Explorer, click the Types tab, and then Click Repository.
7. In the Repositories list view, 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.
8. Locate your current Siebel Repository in the list applet.
9. Click on the name and change it to Prior Customer Repository.

   When you rename the repository, you may prefix the name with additional characters (except for a leading space). Do not append the repository name with additional characters, because this results in an error.

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

   TIP:   Prefix the repository name with a date; for example, 20031202 Prior v6.2.1 Customer Repository.

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

    If no repository is named Prior Customer Repository, the upgrade process renames the Siebel Repository to Prior Customer Repository.