Siebel Database Upgrade Guide > Performing the Siebel Repository Merge >

Preparing for the Repository Merge

Environments: Development environment only.

The process of merging repositories to create a final customized repository used in the upgrade is time-intensive and resource-intensive. As a result, a merge might fail due to environmental factors, such as space constraints. When this happens, the merge process continues, even if there is a fatal database error, and the errors might go undetected.

If the merge fails, then you must restore the database environment to its premerge state and run the repository merge again. Additionally, it is recommended, as another precaution, that you export the New Customer Repository to preserve any existing workflows.

Recovering from a Failed Merge

It is recommended that you perform the following two tasks to preserve the premerge environment in the event of a failed merge.

1. Perform Full Database backup. Prior to the merge, back up the entire database. If the merge fails, then you can restore the database to its premerge state, and rerun the merge operation.
2. Export New Customer Repository. Prior to the merge, export the New Customer Repository to create a backup copy. If the merge fails, then delete the failed repository, then import the backed up copy of the New Customer Repository. See Using Siebel Tools for information on exporting and importing repositories using the Database Configuration Wizard.

   NOTE:  If you export the New Customer Repository, then you must truncate the following merge log tables: S_MERGE_LOG, S_MERGE_LOG_OBJ, and S_MERGE_LOG_ATTR.