In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

2.6

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

oracle 12C

What behaviour do you expect?

When two updates are executed in a transaction, two records will appear.

What behaviour do you see?

Only one record.

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

(Ideally, also verify with latest Alpha/Beta/CR version)

yes.

How to reproduce the issue using our tutorial deployment?

CREATE TABLE "TEST"."TEST_CLOB_NO_PK"

( "NAME" VARCHAR2(100),

"DESC" CLOB

)
UPDATE "TEST".TEST_CLOB_NO_PK SET "DESC"='ccc' WHERE TO_CHAR("DESC")='hhh';

UPDATE "TEST".TEST_CLOB_NO_PK SET "DESC"='aaa' WHERE TO_CHAR("DESC")='eee';

Implementation ideas (optional)

io.debezium.connector.oracle.logminer.processor.TransactionCommitConsumer#acceptDmlEvent

do not merge when there is no primary key.