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.5.0.Final

What is the connector configuration?

{ "name": "source", "config": \{ "connector.class": "io.debezium.connector.oracle.OracleConnector", "include.ddl.changes": "false", "max.queue.size": "16384",  "tasks.max": "1", "query.fetch.size": "10000", "signal.enabled.channels": "source,kafka", "log.mining.strategy": "online_catalog", "schema.history.internal.store.only.captured.tables.ddl": "false", "kafka.consumer.offset.commit.enabled": "false", "topic.prefix": "server1", "decimal.handling.mode": "precise", "schema.history.internal.kafka.topic": "schema-changes", "poll.interval.ms": "50", "signal.kafka.groupId": "kafka-signal", "lob.enabled": "false", "log.mining.sleep.time.max.ms": "30", "database.user": "c##dbzuser", "database.dbname": "ORCLCDB", "signal.kafka.bootstrap.servers": "kafka:9092", "signal.kafka.topic": "signal.kafka", "log.mining.sleep.time.default.ms": "10", "time.precision.mode": "connect", "internal.log.mining.transaction.snapshot.boundary.mode": "all", "schema.history.internal.kafka.bootstrap.servers": "kafka:9092", "snapshot.max.threads": "20", "schema.history.internal.skip.unparseable.ddl": "true", "database.port": "1527", "log.mining.restart.connection": "true", "log.mining.sleep.time.increment.ms": "2", "database.hostname": "192.168.1.115", "log.mining.query.filter.mode": "in", "database.password": "dbz", "name": "source", "table.include.list": "C##DBZUSER.TEST_SJJ_2", "max.batch.size": "4096", "snapshot.mode": "initial", "signal.kafka.poll.timeout.ms": "100" }

}

 

 

{ "name": "sink-1-C_DBZUSER-TEST_SJJ_2", "config": { "connector.class": "io.debezium.connector.jdbc.JdbcSinkConnector", "dialect.name": "PostgreSqlDatabaseDialect", "table.name.format": "public.TEST_SJJ_2", "connection.password": "postgres", "primary.key.mode": "record_key", "tasks.max": "1", "topics": "server1.CDBZUSER.TEST_SJJ_2", "connection.username": "postgres", "transforms": "unwrap", "quote.identifiers": "true", "transforms.unwrap.add.headers": "source.ts_ms,op", "delete.enabled": "true", "schema.evolution": "basic", "transforms.unwrap.drop.tombstones": "false", "name": "sink-1-C_DBZUSER-TEST_SJJ_2", "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState", "connection.url": "jdbc:postgresql://192.168.1.115:5440/postgres", "insert.mode": "upsert" }}

What is the captured database version and mode of depoyment?

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

19c

What behaviour do you expect?

delete can perform correct

What behaviour do you see?

delete can't perform

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

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

<Your answer>

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>