Siebel Database Upgrade Guide for DB2 UDB 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 pre-merge state and run the merge again. There are two methods you can use to preserve the pre-merge environment so that you can restart the merge again if you need to. Before beginning the merge you can either:

• Backup the entire database schema then, if the merge fails, you can restore the schema and rerun the merge. The disadvantage of this option is that it is time consuming and disk space intensive.
• Export the New Customer Repository to create a backup copy. This is a simpler option. If the merge fails, import the New Customer Repository. See Using Siebel Tools for information on exporting and importing repositories using the Database Configuration Wizard.