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_HOME\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.