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

Reviewing Attribute Conflicts in the Repository Merge

Upgrades: All upgrades.

Environments: Development environment only.

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

You can change how attribute conflicts were resolved during the repository merge.

How Attribute Conflicts Occur

Attributes, such as color and height, are defined on repository objects. An attribute conflict occurs in the repository merge when all of the following are true:

• The object and attribute exist in the Prior Siebel Repository, the Prior Customer Repository, and the New Siebel Repository.
• You have changed an attribute value in the Prior Customer Repository. (The attribute value in the Prior Customer Repository and the Prior Siebel Repository are not the same.)
• The attribute has been changed in the New Siebel Repository. (The attribute in the New Siebel Repository and the Prior Siebel Repository are not the same.)

If the values in the Prior Siebel Repository and New Siebel Repository are the same but the value in the Prior Customer Repository is different, there is no conflict. The value in the Prior Customer Repository is preserved in the merged repository.

The merge process resolves attribute conflicts by referring to the setting of the Standard Win property. For about 90% of repository objects, the merge process resolves attribute conflicts by using the attribute values in the New Siebel Repository. Do not change the setting of this property.

Application Upgrade Attribute List View

You can review and change how attribute conflicts were resolved using the Application Upgrade Attribute List view in Siebel Tools. The Attribute Differences List in the view includes the following columns:

• Object Name. The name of the object on which the attribute is defined.
• Attribute. The attribute name.
• Conflict. The merge process puts a check mark in this field if there was an attribute conflict during the merge.
• Resolution. Displays which attribute value the merge process used to resolve the conflict:
  • Standard Value. The attribute value in the New Siebel Repository was used. This value is displayed in the New Standard column.
  • Custom Value. The attribute value in the Prior Customer Repository was used. This value is displayed in the Prior Customized column.
• Override. Put a check mark in this column to change how the attribute conflict is resolved. Overriding the resolution changes the attribute value in the merged repository. If the resolution was the Standard Value it is switched to the Custom Value and vice versa.

  Putting a check mark in the Override column does not change the value displayed in the Resolution column. It indicates that the displayed value was manually overridden in the merged repository.

• Prior Standard. Displays the value of the attribute in the Prior Siebel Repository.
• Prior Customized. Displays the value of the attribute in the Prior Customer Repository. In the Resolution column, this value is called the Custom Value.
• New Standard. Displays the value of the attribute in the New Siebel Repository. In the Resolution column, this value is called the Standard Value.

Prerequisite: The repository merge must have been successful. See Determining if a Repository Merge was Successful.

To review attribute conflicts

1. In Siebel Tools, navigate to Screens > Application Upgrader > Application Upgrade Attribute List.
2. In the Application Upgrades list, select the record of the successful merge.
3. In the Attribute Differences list, click Query.
4. In the Attribute Differences list, click in the Conflict field so that a check mark appears.
5. Press Enter to run the query.

   The query displays a list of all object attributes for which there is a conflict.

6. For each record, review the entry in the Resolution field.
7. To change the resolution, click in the Override field.

   A check mark appears. This changes the value of the attribute in the merged repository.

   Avoid overriding conflicts for the following attributes. Visually review these attribute changes in the upgraded application before changing them:

   • Left
   • Right
   • Top
   • Height
   • Width