Perform Repository Merge

Caution: The Repository merge process cannot be stopped and restarted so make sure you have backed up the database schema or the New Customer Repository before starting the merge.

1. Performing a Siebel Repository Merge.

   Note: If you are upgrading from Siebel CRM version 8.1.1.x (SIA repository) to Siebel CRM 16.0 or later, refer to Performing the Incremental Repository Merge instead of this topic.

2. Review the Siebel Repository merge log files. For information on this task, see the chapter about performing the Siebel Repository merge in Siebel Database Upgrade Guide.

3. If the repository merge contains unacceptable errors, do the following:

   1. Restore the backup of the database or New Customer Repository. See About Backing Up the New Customer Repository or Database Schema.

   2. Correct the errors.

   3. Rerun the repository merge.

   Note: Before completing the next two steps (Step 4 and Step 5), you must execute the Full Publish command in Siebel Tools to generate the Runtime Repository data.

4. Run the Siebel postmerge utilities. For information on this task, see the chapter about performing the Siebel Repository merge in Siebel Database Upgrade Guide.

   This step is required only for full repository merge and not if you are performing an incremental repository merge.

5. Perform the following tasks. For information on these tasks, see the chapter about performing the Siebel Repository merge in Siebel Database Upgrade Guide:

   • Delete unneeded Siebel repository files.

   • Generate Siebel Enterprise Integration Manager (EIM) temporary columns.

   • (Optional) Set label alignment for Siebel text fields.

6. Generate database statistics for new tables and new indexes using the RUNSTATS utility. Your DBA can check the system catalog to determine the database objects that do not have statistics.

   For further information on generating database statistics, see Generating RUNSTATS Jobs.

7. Back up the Siebel database.