Do uncommitted Oracle transactions result in latency on Qlik Replicate tasks?

[MoeE]

Hi,

I read a community post which said that uncommitted transactions on the source would result in source latency to increase on the task until the transaction is complete. However, I tested this by creating an uncommitted transaction on the source Oracle database yet I was unable to recreate this behaviour. I am on QR 2025.11.0.437. Why is this happening? Is this the expected behavior?

Help with this is appreciated. 

Thank you,

Mohammed

[john_wang]

Hello Mohammed, @MoeE 

Thanks for opening the post.

You're right. For an Oracle source database, change events in the REDO logs can be read before the corresponding transactions are committed or rollback under the regular configuration.

Qlik Replicate will then wait for the transaction's COMMIT or ROLLBACK signal to determine how to proceed:

• COMMIT: Apply the changes to the target.

• ROLLBACK: Discard the cached changes from memory.

This behavior itself should not introduce additional latency.

Hope this helps.

John.

[tara096morgan]

Hello,

An uncommitted transaction doesn’t always cause Source Latency to increase. It can depend on the transaction size, duration, and how Replicate is processing the Oracle redo logs. Paybyplatema