We need to check whether or not LogMiner requires explicit transaction boundaries.

A user on Gitter reported using Dbeaver to perform an UPDATE on a table and that it would be auto-committed; however LogMiner never picked up the COMMIT redo log entry and therefore the transaction buffer was never flushed. When the user performed another UPDATE operation wrapping it within an explicit BEGIN/COMMIT wrapper, the DML operations were flushed and available in Kafka.

The user was on Oracle 12, using default LogMiner configurations, no special strategies.