log.mining.transaction.retention.hours should reference last offset and not sysdate

What Debezium connector do you use and what version?

2.1

What is the connector configuration?

Oracle with logminer

What is the captured database version and mode of depoyment?

on-prem. Oracle RAC.

What behaviour do you expect?

If the collector is currently processing a backlog, I would expect the retention hours to reference a time span relating to the currently processed SCN.

What behaviour do you see?

Currently, the rentention hours are referenced to sysdate which can potentially cause a corruption if the collector is processing a backlog

Do you see the same behaviour using the latest relesead Debezium version?

yes

Implementation ideas (optional)

Change the implementation to reference lastProcessedScn instead of sysdate