Siebel Database Upgrade Guide > Performing the Siebel Repository Merge >

Reviewing the Siebel Repository Merge Log Files

Environments: Development environment only.

Platforms: Windows, UNIX, IBM z/OS.

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 the ancestor object is not present in the New Siebel Repository, this causes a merge error. This is an acceptable error and can be ignored.

  Here is an example of an acceptable error in the merge log file, merge0.txt:

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

• Unacceptable errors. All other types of merge errors are unacceptable errors and mean that the merge was not successful.

  For more detailed information, go to 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 repository merge log:

SIEBEL_TOOLS_ROOT\bin\merge0.txt

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

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:

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

If the repository merge terminates and is flagged as Incomplete, then the merge must be restarted, as discussed in Performing a Siebel Repository Merge.

To determine whether the repository merge was successful

1. In Siebel Tools, from the Screens menu, choose Application Upgrader, and then Application Upgrade Object List.
2. In the Application Upgrades list, select the record of the merge.
3. Check the entry in the Status column.
   • Completed. This means the merge completed without errors.
   • Completed with Errors. This means the merge contains errors.

     If the Status column indicates Completed, then no further action is required. The merge was successful.

     If the Status column indicates Completed with Errors, then you must review the errors to determine whether the merge was successful. To review the errors, complete the remaining steps in this task.

4. In the Object Differences list, click Query.
5. In the Status field, enter ERROR::* .
6. Press Enter to run the query.

   This displays all the objects where the merge process encountered errors.

7. Open the merge log file, merge0.txt. It is located in the following directory:

   SIEBEL_TOOLS_ROOT\bin

   If there are multiple files, then open the one with the highest number in the file name, for example merge1.txt.

8. To locate merge errors in the file, search for the !!ERROR string.

   Additionally, informational messages are marked as !!INFO.

9. Use the objects displayed in the Object Differences list and the errors displayed in the log file to analyze the errors:
   • If all the errors are acceptable, then the merge is considered successful.

     It is advisable, however, to consider the number of acceptable errors when determining whether to re-run the merge operation.

   • If the log contains unacceptable errors, then the merge has failed.
10. If the merge contains unacceptable errors, then go to 477269.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Troubleshooting Steps 19.

    This document explains the meaning of many of the error messages that can appear in the log file. Use this document to correct the errors. If you cannot resolve all the errors, then contact Oracle Global Customer Support.

11. Open the workflow merge log file:

    SIEBEL_TOOLS_ROOT\bin\merge0_ver.txt

    If there are multiple files, then open the one with the highest number in the file name, for example merge1_ver.txt. This log file is created by the workflow premerge and postmerge steps.

12. Review the log file. If the file contains errors, then create a service request (SR) on My Oracle Support, or contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.

Related Topics

About the Siebel Repository Merge

Upgrade Planning for Siebel Workflow Designer