AVOID Complete Refresh Required when there is an Un-resolved Conflict
(Doc ID 403955.1)
Last updated on APRIL 14, 2022
Applies to:
Oracle Lite - Version 10.2.0.1.0 to 10.2.0.2.1 [Release 10.2]Information in this document applies to any platform.
Affected Database: Oracle
Goal
When the MGP Apply Data fails because of an Un-resolved conflict, for example: the Client inserted a row which does not have a valid Foreign Key on the Server, then the MGP process will Trigger a Complete refresh on all the items to guarantee data consistency on the client and the server.
To avoid the default behavior custom DML procedures could be implemented so that the errors are handled inside the procedures instead of MGP.
Another way is to use queue-based synchronization where MGP is not involved at all.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |