Siebel Database Upgrade Guide > Performing the Siebel Repository Merge >

Reviewing the Siebel Repository Merge Log Files

Upgrades from: All Supported Siebel releases.

Environments: Development environment only.

Platforms: Windows, UNIX, IBM z/OS.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

To determine if 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 postmerge utilities 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 (Doc ID) on OracleMetalink 3, 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:

Tools_install_dir\bin\merge0.txt

where

Tools_install_dir is the directory in which Siebel Tools is installed.

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

If your repository merge process terminates and is flagged as "Incomplete" under Siebel Tools, Screens > Application Upgrader, 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 is terminated and flagged as 'Incomplete', this should be restarted as discussed in Performing a Siebel Repository Merge.

To determine if the repository merge was successful

1. In Siebel Tools, navigate to Screens > Application Upgrader > 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, no further action is required. The merge was successful.

     If the Status column indicates Completed with Errors, you must review the errors to determine if 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:

   Tools_install_dir\bin

   where

   Tools_install_dir is the directory in which Siebel Tools is installed.

   If there are multiple files, 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, 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, the merge has failed.
10. If the merge contains unacceptable errors, go to 477269.1 (Doc ID) on OracleMetalink 3. 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 contact Oracle Global Customer Support.

11. Open the workflow merge log file:

    Tools_install_dir\bin\merge0_ver.txt

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

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

Related Topics

477269.1 (Doc ID) on OracleMetalink 3. This document was previously published as Siebel Troubleshooting Steps 19.

About the Siebel Repository Merge

Upgrade Planning for Siebel Workflow Designer