Siebel Database Upgrade Guide for DB2 for z/OS > Performing the Siebel Repository Merge >

About Backing Up the New Customer Repository or Database Schema

Upgrades: 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 the final customized repository used in the upgrade is time-intensive and resource-intensive. As a result, a merge might sometimes fail because of environmental factors, for example, space constraints. When this happens, the merge process continues, even if there is a fatal database error, and the errors might not be detected for some time.

If the merge fails, you must restore the database environment to its premerge state and run the merge again. There are two methods you can use to preserve the premerge environment so that you can restart the merge again if necessary:

• Back up the entire database. Prior to the merge, back up the entire database, then, if the merge fails, you can restore the database to its premerge state and rerun the merge operation. This is the recommended method of recovering from a failed merge.
• Export the New Customer Repository. Prior to the merge, export the New Customer Repository to create a backup copy; this preserves existing workflows. If the merge fails, you can delete the failed repository, then import the backup copy of the New Customer Repository. If you use this method of recovering from a failed merge, you also have to truncate the following merge log tables: S_MERGE_LOG, S_MERGE_LOG_OBJ, and S_MERGE_LOG_ATTR. See Using Siebel Tools for information on exporting and importing repositories using the Database Configuration Wizard.