Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
Hello @sush_1 ,
Thanks for reaching out!
This is normal behavior if you are run huge size changes in a single transaction in source side Oracle database. I'm assuming the process is: begin a transaction; update many number of rows; commit the transaction. and repeat the similar operations in source DB.
From Replicate perspective, Replicate detects the changes from REDO Log, then start reading the changed rows from source DB and repeat the read until get COMMIT or ROLLBACK flag so far Replicate knows how to handle the transaction: commit to target, or discard the whole transaction. Before Replicate get the COMMIT/ROLLBACK, the latency builds up and you see latency is increasing in GUI, until it drop down to 0 sometimes.
If you want to get smaller latency, then splitting the huge number changes into multiple smaller transaction may help.
Regards,
John.