Upgrade Guide for DB2 UDB for z/OS > Performing the Siebel Tools Repository Merge >

Determining If a Repository Merge Was Successful

Upgrades: All upgrades.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

The repository 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.

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.

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

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.

   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 ! (exclamation point).
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 successful.
   • If the log contains unacceptable errors, the merge has failed.
10. If the merge contains unacceptable errors, go to My Oracle Support and search for 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.