Oracle Logminer: snapshot->stream switch misses DB changes in ongoing transactions

In Oracle 19c -- the steps below were done through SQL *Plus, which does not auto- commit create table txtest(id int primary key , val varchar2 (100)); grant select on txtest to c ##dbzuser; alter table txtest add supplemental log data ( all ) columns ; insert into txtest values (1, 'pre-snapshot' ); commit ; -- start a new transaction here; this one straddles the snapshot->streaming switch insert into txtest values (2, ' in tx, pre-snapshot' ); -- Now set up a debezium connector for table txtest, wait for the snapshot phase to complete -- as expected only row 1 (pre-snapshot) appears on Kafka insert into txtest values (3, ' in tx, post-snapshot' ); commit ; -- this transaction is fully handled in streaming mode insert into txtest values (4, 'post-tx, streaming' ); commit ; Debezium will only output change records for rows 1 (TX completed pre-snapshot) 3 (TX that spans snapshot->streaming switch: Debezium only records post-switchover changes) 4 (TX lifetime was completely in the streaming phase) The change record for row 2 is never emitted, simply because the logs are never mined that far back. I have attached the Kafka Connect logs captured during the reproduction scenario (io.debezium.connector.oracle.logminer logs at TRACE level, the rest at INFO level). The salient bits start around line 2127.