About the Repository Merge
The configuration utility that you ran while upgrading your development environment loaded two standard repositories. You must now use Siebel Tools to merge your existing custom configuration into one of these new repositories, creating a custom configuration that includes all of your previous configuration changes.
The four repositories that currently exist in your development database are listed in the following table.
| Repository Name | Description |
|---|---|
Prior Siebel Repository |
Standard repository, depending on the version from which you are upgrading. |
Prior Customer Repository |
Customized repository, depending on the version from which you are upgrading. |
New Siebel Repository |
Newly loaded standard repository. |
New Customer Repository |
Newly loaded repository into which your custom configuration is merged. |
Follow the guidelines provided in Optimizing Performance of the Repository Merge and Optimizing Foreground Performance of the Repository Merge to improve performance of the repository merge.
The repository merge is a memory-intensive process that fails if insufficient memory is available on the Siebel Tools workstation. Before beginning a repository merge, make sure that the following preparations have been completed on the developer workstation. Make sure that the developer workstation on which Siebel Tools is running has been upgraded to the newest available version.
The method you use to perform a repository merge depends on whether your database uses an ASCII or EBCDIC encoding scheme:
For ASCII databases, perform the procedure, Merging the Repositories for an ASCII Database.
For EBCDIC databases, perform the procedure, Merging Repositories for an EBCDIC Database.