-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
1.8.1.Final
-
None
-
None
-
False
-
None
-
False
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?
I'm running Debezium Oracle connector version 1.8.1.Final.
What is the connector configuration?
Below is my connector configuration
{ "name": "###-custom-connector-v3", "config":
{ "name": "star-custom-connector-v3", "connector.class": "io.debezium.connector.oracle.OracleConnector", "tasks.max": "1", "transforms": "changeTopicCase", "transforms.changeTopicCase.type": "com.github.jcustenborder.kafka.connect.transform.common.ChangeTopicCase", "transforms.changeTopicCase.from": "UPPER_UNDERSCORE", "transforms.changeTopicCase.to": "LOWER_UNDERSCORE", "database.hostname": "###", "database.port": "1521", "database.user": "kminer", "database.password": "**********", "database.server.name": "###", "database.dbname": "###", "snapshot.mode": "initial", "database.connection.adapter": "logminer", "log.mining.strategy": "online_catalog", "internal.database.oracle.version": "v1", "max.batch.size": "2048", "poll.interval.ms": "1000", "snapshot.fetch.size": "5000000", "snapshot.max.threads": "20", "query.fetch.size": "0", "decimal.handling.mode": "double", "time.precision.mode": "connect", "log.mining.archive.log.only.mode": "false", "database.history.skip.unparseable.ddl": "true", "database.history.kafka.bootstrap.servers": "broker:29092", "database.history.kafka.topic": "dbhistory.star", "sanitize.field.names": "true", "tombstones.on.delete": "true", "signal.data.collection": "###.###.DBZ_SIGNAL", "column.exclude.list": "###.###.IMAGE, ###.###.ICON, ###.###.CUSTOMIMAGE", "table.include.list": "###.###, ###.DBZ_SIGNAL", "message.key.columns": "###.ATTACHMENTGROUP:ATTACHMENTGROUPID; ###.DBZ_SIGNAL:ID;" }}
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
The Capture database is Oracle 11g on premise.
What behaviour do you expect?
I'm trying to use the "signal.data.collection" feature in the connector. I would like to do a incremental snapshot on a table.
What behaviour do you see?
This is the error log... I'm running an old version of Oracle 11g and this version doesn't support " DESC FETCH NEXT 1 ROWS ONLY" in the sql select
connect | [2022-05-03 10:59:27,062] ERROR WorkerSourceTask{id=star-custom-connector-v3-0} Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask)
connect | org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
connect | at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:42)
connect | at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:191)
connect | at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:57)
connect | at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:172)
connect | at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:139)
connect | at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:108)
connect | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
connect | at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
connect | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
connect | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
connect | at java.base/java.lang.Thread.run(Thread.java:829)
connect | Caused by: org.apache.kafka.connect.errors.ConnectException: Error while processing event at offset {commit_scn=112668644094, transaction_id=null, incremental_snapshot_maximum_key=aced000570, snapshot_pending_tx=, snapshot_scn=112668640779, incremental_snapshot_collections=###.###.ATTACHMENTGROUP, incremental_snapshot_primary_key=aced000570, scn=112668644087}
connect | at io.debezium.pipeline.EventDispatcher.dispatchDataChangeEvent(EventDispatcher.java:252)
connect | at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor$1.accept(AbstractLogMinerEventProcessor.java:407)
connect | at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor$1.accept(AbstractLogMinerEventProcessor.java:363)
connect | at io.debezium.connector.oracle.logminer.processor.TransactionCommitConsumer.dispatchChangeEvent(TransactionCommitConsumer.java:247)
connect | at io.debezium.connector.oracle.logminer.processor.TransactionCommitConsumer.accept(TransactionCommitConsumer.java:104)
connect | at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.handleCommit(AbstractLogMinerEventProcessor.java:425)
connect | at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.processRow(AbstractLogMinerEventProcessor.java:271)
connect | at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.processResults(AbstractLogMinerEventProcessor.java:241)
connect | at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.process(AbstractLogMinerEventProcessor.java:187)
connect | at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:178)
connect | ... 9 more
connect | Caused by: io.debezium.DebeziumException: Database error while executing incremental snapshot for table '###.###.ATTACHMENTGROUP'
connect | at io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource.readChunk(AbstractIncrementalSnapshotChangeEventSource.java:312)
connect | at io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource.addDataCollectionNamesToSnapshot(AbstractIncrementalSnapshotChangeEventSource.java:398)
connect | at io.debezium.pipeline.signal.ExecuteSnapshot.arrived(ExecuteSnapshot.java:56)
connect | at io.debezium.pipeline.signal.Signal.process(Signal.java:137)
connect | at io.debezium.pipeline.signal.Signal.process(Signal.java:175)
connect | at io.debezium.pipeline.EventDispatcher$2.changeRecord(EventDispatcher.java:226)
connect | at io.debezium.relational.RelationalChangeRecordEmitter.emitCreateRecord(RelationalChangeRecordEmitter.java:78)
connect | at io.debezium.relational.RelationalChangeRecordEmitter.emitChangeRecords(RelationalChangeRecordEmitter.java:46)
connect | at io.debezium.pipeline.EventDispatcher.dispatchDataChangeEvent(EventDispatcher.java:215)
connect | ... 18 more
connect | Caused by: java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
connect | at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
connect | at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
connect | at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1052)
connect | at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:537)
connect | at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:255)
connect | at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:610)
connect | at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:213)
connect | at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:37)
connect | at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:724)
connect | at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:921)
connect | at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1099)
connect | at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1293)
connect | at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:366)
connect | at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:644)
connect | at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:513)
connect | at io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource.readChunk(AbstractIncrementalSnapshotChangeEventSource.java:274)
connect | ... 26 more
connect | Caused by: Error : 933, Position : 82, Sql = SELECT * FROM "ENERGOVSERVER"."ATTACHMENTGROUP" ORDER BY "ATTACHMENTGROUPID" DESC FETCH NEXT 1 ROWS ONLY, OriginalSql = SELECT * FROM "ENERGOVSERVER"."ATTACHMENTGROUP" ORDER BY "ATTACHMENTGROUPID" DESC FETCH NEXT 1 ROWS ONLY, Error Msg = ORA-00933: SQL command not properly ended
connect |
connect | at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
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>
