Debezium Incremental Snapshot via Signal Table Not Initiating

[Ramesh K]

Hi Chris,

I have successfully deployed Debezium 2.5 with Oracle 12c in schema-only mode, and Change Data Capture (CDC) is operational. However, I am encountering an issue when attempting to initiate an incremental snapshot via the signaling table. The snapshot process is not commencing, and no corresponding logs or error messages are being generated. It is important to note that the identical signal format statement functions correctly with a different Oracle source database.

The sole distinction between these two configurations lies in the database naming convention. The database where the signal snapshot is failing utilizes a service name (e.g., dbname.com), whereas the database where the signal snapshot is successful does not incorporate a service name.

How to make sure that snapshot is initiated.

My inquiry pertains to the configuration of signal data collection. Specifically, regarding the format "dbname.dbuser.signal table," should the "dbname" component refer to the service name or simply the database name?

Below is config used 

Your guidance, on this matter would be greatly appreciated.

Thanks in advance.

 "name": "****",

  "config": {

    "topic.creation.default.partitions": "3",

    "incremental.snapshot.chunk.size": "1000000",

    "schema.history.internal.consumer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"*****\" password=\"*****\";",

    "value.converter.schema.registry.basic.auth.user.info": "******9",

    "schema.history.internal.kafka.topic": "*****",

    "schema.history.internal.producer.security.protocol": "SASL_SSL",

    "topic.creation.default.replication.factor": "-1",

    "schema.history.internal.producer.sasl.mechanism": "PLAIN",

    "schema.history.internal.consumer.ssl.endpoint.identification.algorithm": "https",

    "value.converter.schema.registry.basic.auth.credentials.source": "USER_INFO",

    "schema.history.internal.kafka.bootstrap.servers": "*****",

    "schema.history.internal.producer.ssl.endpoint.identification.algorithm": "https",

    "value.converter.schema.registry.url": "ht*****",

    "schema.history.internal.consumer.sasl.mechanism": "PLAIN",

    "schema.history.internal.producer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"*****\" password=\"***\";",

    "key.converter.schema.registry.basic.auth.user.info": "**:*****",

    "key.converter.schema.registry.basic.auth.credentials.source": "USER_INFO",

    "key.converter.schema.registry.url": "https*******",

    "schema.history.internal.consumer.security.protocol": "SASL_SSL",

    "name": "****",

    "connector.class": "io.debezium.connector.oracle.OracleConnector",

    "tasks.max": "1",

    "key.converter": "io.confluent.connect.avro.AvroConverter",

    "value.converter": "io.confluent.connect.avro.AvroConverter",

    "transforms": "unwrap",

    "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",

    "transforms.unwrap.drop.tombstones": "false",

    "topic.prefix": "****",

    "database.hostname": "****",

    "database.port": "**",

    "database.user": "***",

    "database.password": "***",

    "database.dbname": "dbname",

    "snapshot.mode": "schema_only",

    "log.mining.strategy": "online_catalog",

    "decimal.handling.mode": "double",

    "log.mining.archive.destination.name": "LOG_ARCHIVE_DEST_5",

    "log.mining.query.filter.mode": "none",

    "schema.history.internal.skip.unparseable.ddl": "true",

    "schema.history.internal.store.only.captured.tables.ddl": "true",

    "schema.history.internal.store.only.captured.databases.ddl": "true",

    "heartbeat.interval.ms": "60000",

    "signal.data.collection": "**  dbname.DBUSER.DEBEZIUM_SIGNAL",

    "column.exclude.list": "****",

    "table.include.list": "***"

[Chris Cranford]

Hi Ramesh -

I believe I answered this on Zulip; but in case I did not.

The issue here is when your database name contains a "." character, you need to quote the table identifier so that its properly parsed. So in your case, it should be:

    "\"dbname.com\".YOUR_SCHEMA.YOUR_TABLE"

You'll notice that the database name is surrounded by escaped quote characters, which guarantees that the `.` character in the database name is not treated as a delimiter but rather as part of the database name.

Hope that helps.
-cc