1. Database Upgrade Guide
  2. Reviewing the Siebel Repository Merge Log Files

Reviewing the Siebel Repository Merge Log Files

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

Environments: Development environment only.

Platforms: Windows, UNIX, IBM z/OS.

  • Acceptable errors. If an ancestor object is specified in an object definition, and the ancestor object isn'tpresent in the New Siebel Repository, this causes a merge error. This is an acceptable error and can be ignored.

    Here's 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 wasn't successful.

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_HOME\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. From the Screens menu in Siebel Tools, choose Application Upgrader, and then Application Upgrade Object List.

  2. In the Application Upgrades list, select the record of the merge.

  3. Review the entry in the Status column:

    • Completed. Indicates the merge completed without errors.

    • Completed with Errors. Indicates 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.

      Note: These errors don't indicate an incomplete merge and rerunning the merge will not correct them.

  4. In the Object Differences list, click Query.

  5. In the Status field, enter the following: !!ERROR::*

  6. Press Enter to run the query. A list of objects where the merge process found errors is returned.

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

    $SIEBEL_HOME\bin\merge0.txt

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

  8. To find merge errors in the file, search for the !!ERROR string. 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's 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.

    If you can't resolve all the errors, then contact Oracle Support.

  10. Open the workflow merge log file:

    $SIEBEL_HOME\bin\merge0_ver.txt

    If there are multiple files, then open the file 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.

  11. Review the log file. If the file contains errors, then create a service request (SR) on My Oracle Support, or contact your Oracle salesperson for Oracle Advanced Customer Services to request help from Oracle’s Application Expert Services.

Related Topics