Details
-
Bug
-
Resolution: Done
-
Major
-
1.9.4.Final, 2.0.0.Alpha2
-
None
-
False
-
None
-
False
Description
Bug report
What Debezium connector do you use and what version?
Oracle Connector 2.0.0.Alpha2
Oracle Connector 1.9.4.Final
What is the connector configuration?
A little sanitized, but should be sufficient I hope:
{
"connector.class": "io.debezium.connector.oracle.OracleConnector",
"database.connection.adapter": "logminer",
"database.dbname": "DATA.BIZ.GRP",
"database.history.consumer.sasl.jaas.config": "",
"database.history.consumer.sasl.mechanism": "",
"database.history.consumer.security.protocol": "",
"database.history.kafka.bootstrap.servers": "",
"database.history.kafka.topic": "schema-changes-p.internal",
"database.history.producer.sasl.jaas.config": "",
"database.history.producer.sasl.mechanism": "",
"database.history.producer.security.protocol": "",
"database.hostname": "",
"database.password": "",
"database.port": "1521",
"database.server.name": "p",
"database.user": "dbzuser",
"decimal.handling.mode": "string",
"event.processing.failure.handling.mode": "fail",
"log.mining.strategy": "online_catalog",
"max.queue.size": "4096",
"name": "p-connector",
"provide.transaction.metadata": "true",
"signal.data.collection": "DATA.BIZ.GRP.DBZUSER.DEBEZIUM_SIGNAL",
"snapshot.mode": "initial",
"table.include.list": "DBZUSER.DEBEZIUM_SIGNAL,SCHEMA.SESSIONS, ..., SCHEMA.USERS",
"tasks.max": "1",
"topic.creation.default.partitions": "6",
"topic.creation.default.replication.factor": "3"
}
What is the captured database version and mode of depoyment?
Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production Version 19.11.0.0.0
On Prem
What behaviour do you expect?
Incremental snapshot of the specified table DATA.BIZ.GRP.SCHEMA.CREDENTIAL_TYPES
What behaviour do you see?
I see an error that the schema of the table DATA.BIZ.GRP is not found. The connector suggests valid table names, which again includes the table I specified. Obviously, using the suggested names leads to the same error.
It looks to me like periods in database names can't be parsed or more specifically the parsing only uses the first three entries when splitting the table name by period.
Do you see the same behaviour using the latest relesead Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
Statement:
| ID | TYPE | DATA |
|---|---|---|
| fe4b07d2-47ce-4435-927b-08ecae14514d | execute-snapshot | {"data-collections": ["DATA.BIZ.GRP.SCHEMA.CREDENTIAL_TYPES"]} |
Logs:
2022-06-30T09:28:54:029z INFO Oracle|p|streaming Requested 'INCREMENTAL' snapshot of data collections '[DATA.BIZ.GRP.SCHEMA.CREDENTIAL_TYPES]' [io.debezium.pipeline.signal.ExecuteSnapshot] 2022-06-30T09:28:54:067z WARN Oracle|p|streaming Schema not found for table 'DATA.BIZ.GRP', known tables [DATA.BIZ.GRP.SCHEMA.CREDENTIAL_TYPES, ..., DATA.BIZ.GRP.SCHEMA.USERS] [io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource] 2022-06-30T09:28:57:308z INFO Oracle|p|streaming Skipping read chunk because snapshot is not running [io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource]
How to reproduce the issue using our tutorial deployment?
- Set up an Oracle Database with periods in the name, e.g. DATA.BIZ.GRP
- Create any table within any schema
- Try to perform an incremental snapshot of that table