1. Database Upgrade Guide
  2. Requirements for Restarting the Incremental Repository Merge

Requirements for Restarting the Incremental Repository Merge

Platforms: Windows, UNIX, IBM z/OS.

If the incremental repository merge stops because of errors, then you must review the log files, and restart the merge.

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

  1. Perform a full database backup. Before 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 the new customer repository. Before the merge, export the New Customer Repository to create a backup copy. If the merge fails, then delete the failed repository, and import the backed-up copy of the New Customer Repository. See Using Siebel Tools for information on exporting and importing repositories using the Siebel 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.