Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Database Upgrade Guide > Performing the Siebel Repository Merge > Reviewing Siebel Repository Object Property ConflictsEnvironments: Development environment only. Platforms: Windows, UNIX, IBM z/OS. You can change how object property conflicts were resolved during the repository merge. How Object Property Conflicts OccurThe repository merge compares repository object properties in the Prior Siebel Repository, Prior Customer Repository, and New Siebel Repository. When the value of an object property is different in all three repositories, an object property conflict exists. This occurs when you have changed the value of an object property in the Prior Customer Repository, and the value of this property has also changed in the new release (New Siebel Repository). An object property conflict does not occur if you changed the value of an object property in the Prior Customer Repository, and the object property value did not change in the new release. When this happens, the merge process transfers the changed value to the New Customer Repository. The merge process resolves object property conflicts by referring to the setting of the object's Standard Win property. For about 90% of repository objects, the merge process resolves conflicts by using the object property value in the New Siebel Repository. Do not change the setting of the Standard Win property. Application Upgrade Attribute List ViewYou can review and change how object property conflicts were resolved using the Application Upgrade Attribute List view in Siebel Tools. The Attribute Differences List in the view includes the following columns:
Requirement: The repository merge must have been successful. See Reviewing the Siebel Repository Merge Log Files. To review object property conflicts
Related Topics |
![]() |
![]() ![]() |
Siebel Database Upgrade Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |