The poster opo log displays the following message: “Full rollback transaction 5(40).520507-2(36559) committed” and show post detail rollback count value is incremented
Prior to shareplex 6.1 the post process handled all rollbacks that originated on source. Starting with Shareplex 6.1, capture has a new "skip rollback logic" in which capture and reader process on source began to process some of the rollbacks and remove them from the queue. The read process removes these rollbacks from the queue and then sends a “commit” marker to the post . These out of band messages are in subqueue -2. As a result, the poster opo log displays the following message: “Full rollback transaction 5(40).520507-2(36559) committed” and show post detail rollback count value is incremented. These rollback messages are informational messages written to the opo log when this functionality is used and do not affect shareplex replication.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center