Bookshelf Home | Contents | Index | PDF |
Siebel Remote and Replication Manager Administration Guide > Troubleshooting Siebel Remote > Troubleshooting a Merge Problem > Troubleshooting an Assignment Manager Merge ProblemIf the LogTxnChgOnly (Log Transaction on Change Only) parameter for Assignment Manager is True, then Siebel Remote might log an unusually high number of merge conflicts. You can safely ignore many of these merge conflicts. This topic describes why this situation occurs and includes a scenario that describes how these merge conflicts occur. Why LogTxnChgOnly Affects the Quantity of Merge ConflictsWhen LogTxnChgOnly is True, Assignment Manager does not log transactions for changes that only affect the ASGN_DT field for a record. The ASGN_DT field records the most recent date and time that Assignment Manager assigned that record. This field is not normally visible in a Siebel application. If only the value of the ASGN_DT field changes, then Siebel Remote does not log transactions and it does not send these changes to the remote client. Not sending these changes causes a discrepancy between the record version that is stored on the Siebel Server and the version that is stored in the local database on the remote client. The discrepancy causes no immediate problem because it does not affect the data fields that are visible for the record. Allowing such harmless discrepancies can significantly reduce the amount of data that Siebel Remote must transfer to the remote client during synchronization. If Assignment Manager updates data fields that are visible in the record at a later time, then Siebel Remote logs a transaction. In this situation, Siebel Remote detects the discrepancy in the value of the ASGN_DT field the next time that the remote client attempts a synchronization, and it reports the discrepancy as a merge conflict. Scenario for a Harmless Merge ConflictThis topic gives one example of how a harmless merge conflict occurs. You might experience this merge conflict differently, depending on your business model. For clarity, the value of the ASGN_DT field that this scenario describes is a date only, although the field actually includes date and time. The following sequence of events is an example that produces a harmless merge conflict:
Distinguishing Between a Harmless and a Meaningful Merge ConflictThis topic describes how to distinguish between a harmless merge conflict that is caused by changes to ASGN_DT fields and a potentially meaningful conflict that involves your data. To distinguish between a harmless and a meaningful merge conflict
|
Siebel Remote and Replication Manager Administration Guide | Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |