About the Siebel Repository Merge

Environments: Development environment only.

Platforms: Windows, UNIX, IBM z/OS.

Repositories are located in tables in the Siebel database. These tables store the definitions of the objects used to build Siebel Business Applications. These tables also store Siebel schema definitions. When you display objects in the Siebel Tools Object List Explorer, you are displaying records from these tables.

The repository tables contain three types of records:

Object definitions used to create Siebel Business Applications, such as business components, applets, controls, and the relationships between them.
Definitions of the tables in the Siebel database (metadata). These records define the logical schema of the Siebel database. Later in the upgrade process, you will synchronize the physical schema of the Siebel database with the logical schema as defined by these records.
Runtime Repository tables. The Runtime Repository tables usually begin with S_RR prefix and store the compiled definitions of the repository objects.

Repository records include a repository ID that identifies the repository to which the record belongs. The repository ID forms part of the user index for records and allows several repositories to be stored in the same set of tables.

The Siebel Repository is the deployed, active Siebel Tools repository. You use this repository to customize applications.

The development upgrep adds three additional repositories to the Siebel database, as listed in the following table. These repositories are required for the repository merge.

Repository Name	Added During Upgrade?	Siebel Tools Name	Description
Prior Customer Repository	No	Prior Customized	This is your current Siebel Repository, before upgrading. It contains any changes you have made. You renamed it Prior Customer Repository before doing the initial database upgrade.
Prior Siebel Repository	Yes	Prior Standard	The standard Siebel Repository for your installed release (the release you are upgrading from). Is called the common ancestor repository in the upgrade SQL scripts.
New Siebel Repository	Yes	New Standard	The Siebel Repository for the release to which you are upgrading. This repository defines the new release.
New Customer Repository	Yes	New Customized	A second copy of the New Siebel Repository. Your customizations from the Prior Customer Repository are merged into this repository. After the upgrade, this becomes the Siebel Repository.