-
Bug
-
Resolution: Unresolved
-
Major
-
2.1.4.Final, 2.4.0.Final
-
None
-
False
-
None
-
False
-
Important
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
2.4.0.Final, 2.1.4.Final
What is the connector configuration?
{
"connector.class": "io.debezium.connector.oracle.OracleConnector",
"query.fetch.size": "10000",
"schema.history.internal.consumer.sasl.jaas.config": "${secrets}",
"transforms": "FilterFields",
"heartbeat.action.query": "UPDATE P1QMS.QMS_DEBEZIUM_HEARTBEAT SET BEAT = SYS_EXTRACT_UTC(SYSTIMESTAMP)",
"schema.history.internal.producer.security.protocol": "SASL_SSL",
"schema.history.internal.producer.ssl.truststore.password": "${secrets}",
"signal.data.collection": "PECBOFF3.P1QMS.QMS_DEBEZIUM_SIGNAL",
"heartbeat.topics.prefix": "__debezium-heartbeat",
"key.converter": "org.apache.kafka.connect.json.JsonConverter",
"schema.history.internal.producer.sasl.mechanism": "SCRAM-SHA-512",
"database.dbname": "pecboff3",
"database.user": "${secrets}",
"transforms.FilterFields.type": "com.ahold.debezium.connect.transformation.FilterTableFieldsTransformation",
"heartbeat.interval.ms": "300000",
"schema.history.internal.kafka.bootstrap.servers": "${env:KAFKA_CONNECT_BOOTSTRAP_SERVERS}",
"schema.history.internal.skip.unparseable.ddl": "true",
"key.converter.schemas.enable": "false",
"value.converter.schema.registry.url": "http://schema-registry",
"database.password": "${secrets:draak/debezium-credentials:dbz_password}",
"value.converter.schemas.enable": "false",
"name": "debezium-prd-boff-source",
"schema.history.internal.consumer.sasl.mechanism": "SCRAM-SHA-512",
"schema.history.internal.consumer.ssl.truststore.type": "PKCS12",
"schema.history.internal.producer.sasl.jaas.config": "${secret}",
"max.batch.size": "20480",
"snapshot.mode": "schema_only",
"schema.history.internal.consumer.security.protocol": "SASL_SSL",
"max.queue.size": "81290",
"incremental.snapshot.chunk.size": "10000",
"tasks.max": "1",
"log.mining.strategy": "redo_log_catalog",
"schema.history.internal.store.only.captured.tables.ddl": "true",
"tombstones.on.delete": "false",
"topic.prefix": "PRD.BOFF",
"decimal.handling.mode": "string",
"schema.history.internal.consumer.ssl.truststore.location": "/ca.p12",
"schema.history.internal.kafka.topic": "prd.boff.history-changes",
"transforms.FilterFields.error.mode": "throw_error",
"transforms.FilterFields.cache.expiration.minutes": "60",
"value.converter": "io.confluent.connect.avro.AvroConverter",
"log.mining.transaction.retention.hours": "5",
"transforms.FilterFields.table.exclude.list": "P1QMS.QMS_DEBEZIUM_HEARTBEAT,P1QMS.QMS_DEBEZIUM_SIGNAL",
"log.mining.batch.size.max": "500000",
"database.connection.adapter": "logminer",
"database.url": "${secrets:draak/debezium-credentials:boff_url}",
"schema.history.internal.consumer.ssl.truststore.password": "${secrets}",
"schema.history.internal.producer.ssl.truststore.type": "PKCS12",
"transforms.FilterFields.metadata.service.url": "http://metainfo-service/v1/metainfo/column/",
"schema.name.adjustment.mode": "avro",
"schema.history.internal.producer.ssl.truststore.location": "ca.p12",
"table.include.list": "P1BOFF.BOFF_ORDER,P1QMS.QMS_DEBEZIUM_HEARTBEAT,P1QMS.QMS_DEBEZIUM_SIGNAL"
}
What is the captured database version and mode of depoyment?
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.13.0.0.0
What behaviour do you expect?
-
What behaviour do you see?
Primary key and all not null fields prefilled with default values
key is:
{"NO":0}value is:
{"after":
{"NO":0,"CUST_NO":0,"ORCT_CODE":"","ZIPC_NO":0,"STAT_CODE":"","STCO_STTY_CODE":"","STCO_CODE":"","ORME_NO":0,"DELO_NO":0,"POSL_NO":0,"DELIVERY_ADDRESS":"","HOUSE_NO":0,"STREET":"","CITY":"","ORDER_ENTRY_DATE":0,"SHOC_NO":0},"source":{"version":"2.4.0.Final","connector":"oracle","name":"PRD.BOFF","ts_ms":1696530392000,"snapshot":"false","db":"PECBOFF3","schema":"P1BOFF","table":"BOFF_ORDER","txId":"2c0016002c70dd02","scn":"7590034236013","commit_scn":"7590034236051","rs_id":"0x090611.001f2b60.0010","ssn":0,"redo_thread":1},"op":"c","ts_ms":1696840562026}
Do you see the same behaviour using the latest relesead Debezium version?
yes