Siebel Database Upgrade Guide > Performing the Siebel Incremental Repository Merge > Process of Performing an Incremental Upgrade of the Siebel Database from Siebel CRM Version 8.1.1.x and 8.2.2.x (SIA Repository) >

Preparing to Restart the Merge

Before restarting the merge, considering the following requirements:

If the Siebel Upgrade Wizard encounters an error and exits during an upgrade, then you can restart it after correcting the error. The Siebel Upgrade Wizard reads the state log and continues the upgrade from the last successfully completed step.

If the Siebel Upgrade Wizard stops because of errors, then verify that you have met these requirements before restarting the wizard:

• Carefully review the relevant log files to make sure that your upgrade has completed successfully up to that point.
• Back up your complete set of log files, from the beginning of the process to the point at which it stopped, to another directory.

  This backup maintains a complete record of your log files, and it prevents your previous log files from being overwritten, which might prevent an accurate diagnosis of the reason for the error in the upgrade.

• If you are continuing a previous and incomplete schema upgrade, then do not change the path of the Log Output Directory that you previously selected.
• If problems with your environment prevent the upgrade from restarting, then you must restore the database from the prior base version; that is, the version from which you are upgrading. For example, environment problems might occur when table creation fails because of a database problem (insufficient storage or network problems), which causes subsequent upgrade steps to fail.

  If you want to restore your database and restart the upgrade, then delete or store the upgrade log files. The files are located in the following directory:

  Windows: SIEBEL_ROOT\log\PROCESS\output

  UNIX: $SIEBEL_ROOT/log/PROCESS/output

  Also delete the state.log file. It is located in the following directory:

  Windows: SIEBEL_ROOT\log\PROCESS\state

  UNIX: $SIEBEL_ROOT/log/PROCESS/state

Requirements for Restarting the Incremental Repository Merge

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.

To restart the merge

1. Restore the database to the state of the backup taken before the merge.

   You must have already executed database statistics.

2. Review the irm_sav_file.ssf file located under Siebel Tools Installation directory\bin. The State value should equal 7 (State=7). If it is any other value, then you must change it to 7 before starting the incremental repository merge again.
3. Do one of the following:
   • On a Windows computer. Restart the Execute Incremental Repository Merge task by marking the step as Incomplete in the state.log file located under Siebel Server installation directory \siebsrvr\log\upgrade.
   • On a UNIX computer. Execute the incremental repository merge through the command line on your Windows computer.

     For more information, see Starting the Siebel Upgrade Wizard to restart the upgrade process.