Article

Pro2-How does thread replicate the record if the same record has been changed three time

Information

 
Article Number000093737
EnvironmentProduct: Progress
Product: OpenEdge
Version: All Supported Versions
OS: All Supported Platforms
Other: Pro2, Pro2SQL, Pro2ORA
Question/Problem Description
How does thread replicate the record if the same record has been changed three time 
If the same record has been updated three time in a short time, why only the last value gets replicated to the target
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
In a normal or standard setup, Pro2 does not queue up the changes, it simply records that an "event" has happened on a record in the source database, storing database name, table name, rowid of the affected record and a few other event handling fields (date, time and status, etc.)
When Pro2 encounters an event that needs to be replicated, and that event was not a "delete", then Pro2 re-finds the current copy of the record, by db/table/rowid, and copies current values of all mapped fields to the target db.
If multiple updates to the same source record happen before Pro2 processes the event, then all of the changes to the record are copied when processing the first event. This happens due to the re-read of the source record and the copy to target is based on the "state" of the record at the time of that db read.  When multiple updates to the same row have been queued, the other queue records also get processed, unless queue compression is enabled, but it's basically a resend of all the same data.  
Workaround
Notes
Attachment 
Last Modified Date1/10/2019 1:56 PM


Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025