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) >

Reviewing the Siebel Repository Merge Log Files


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

Environments: Development environment only.

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

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. Review the entry in the Status column as follows:
    • 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 do not 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.

    This step displays all the objects in which the merge process encountered errors.

  7. Open the merge log file, IRM_merge0.txt.

    It is located in the following directory:

    Tools_install_dir\log\IRM_merge0.txt.

    In this path, Tools_install_dir is the directory in which Siebel Tools is installed. If there are multiple files, then open the one with the highest number in the file name, for example, IRM_merge1.txt.

  8. To locate 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 successful.

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

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

    This document explains 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:

    Tools_install_dir\log\IRM_merge0_ver.txt

    If there are multiple files, then open the file with the highest number in the file name, for example, IRM_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.
Siebel Database Upgrade Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.