Siebel Database Upgrade Guide > Performing the Siebel Incremental Repository Merge > Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository) >

About Siebel Repository Merge Errors

This task is a step in Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository). Use this task to review Siebel Repository merge log files.

Environments: Development environment only.

Platforms: Windows, UNIX, and IBM z/OS.

Acceptable and Unacceptable Errors

To determine whether the repository merge was successful, review the merge log files. The merge is successful if it completes without unacceptable errors:

• Acceptable errors. If an ancestor object is specified in an object definition, and if the ancestor object is not present in the New Siebel Repository, then a merge error occurs. This error is acceptable, and you can ignore it. The following is an example of an acceptable error in the merge log file, IRM_merge0.txt:

  !!ERROR::CANNOT upgrade objects which have Briefing Tracking Profile Applet - Product marked as 'Upgrade Anc'.

  If an object already exists in the New Customer Repository that has come from any Release Feature (RF) from Siebel CRM version 8.1.1.x or 8.2.2.x, then a merge error results stating that the object cannot be inserted because the same values already exist. This error is acceptable.

• Unacceptable errors. All other types of merge errors are unacceptable and indicate that the merge was not successful. For more information, see 477269.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Troubleshooting Steps 19.

Merge errors are displayed in the Upgrade Applications Objects List view in Siebel Tools. Additional details on merge errors are located in the incremental repository merge log file:

SIEBEL_TOOLS_ROOT\log\IRM_merge0.txt

Each time you run the merge process, the name of the IRM_merge0.txt file is incremented, for example, to IRM_merge1.txt.

Causes of an Incomplete Merge Process

If your repository merge process terminates and is flagged as Incomplete, then navigate to the Screens menu in Siebel Tools, and choose the Application Upgrader menu item. The most common reasons for its failure are as follows:

• The number of errors (!!ERROR) exceeds the number that was predefined in Siebel Tools when the merge was started.
• The merge process has been terminated because of a local issue on the Siebel Tools workstation, such as a scheduled reboot.
• RDBMS errors caused the process to stop.
• Memory allotment issues occurred on the workstation on which Siebel Tools is installed.
• A network failure occurred.

If the repository merge is terminated and flagged as Incomplete, then restart the incremental repository merge. For more information, see Process of Meeting the Requirements for an Incremental Upgrade to Siebel CRM Version 15.5 or Later, Using the Incremental Repository Merge.