Siebel Database Upgrade Guide > Performing the Siebel Repository Merge >
Preparing for the Repository Merge
All upgrades. This topic applies to all upgrades.
Environments: Development environment only.
This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.
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 may 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 may go undetected.
If the merge fails, you must restore the database environment to its pre-merge state and run the merge again. Additionally, it is recommended, as another precaution, that you export the New Customer Repository to preserve existing workflows.
Recovering from a Failed Merge
It is recommended that you perform the following two tasks to preserve the pre-merge environment in the event of a failed merge.
- Perform Full Database backup. Prior to the merge, back up the entire database, then, if the merge fails, you can restore the database to its pre-merge state, and rerun the merge operation.
- Export New Customer Repository. Prior to the merge, export the New Customer Repository to create a backup copy. If the merge fails, 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, you must truncate the following merge log tables: S_MERGE_LOG, S_MERGE_LOG_OBJ, and S_MERGE_LOG_ATTR.