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?

Oracle Debezium Connector 2.3.4

 

What is the connector configuration?

{
    "name": "amsdev-connector",
    "config":

{         "connector.class": "io.debezium.connector.oracle.OracleConnector",         "tasks.max": "1",         "topic.prefix": "name",         "database.hostname": "ip",         "database.port": "port",         "database.user": "username",         "database.dbname": "dbname",         "database.password": "password",         "database.server.name": "dbname",         "table.include.list": "table.name",         "snapshot.select.statement.overrides": "table_name",         "snapshot.select.statement.overrides.<table_name>": "SELECT * FROM table_name PARTITION (name)",         "database.history.kafka.bootstrap.servers": "ip:9092",         "schema.history.internal.kafka.topic": "amsdevconnector",         "database.history.kafka.topic": "schema-changes",         "schema.history.internal.store.only.captured.tables.ddl": "true",         "schema.history.internal.kafka.bootstrap.servers": "ip:9092",         "snapshot.mode": "schema_only",         "database.history.kafka.retention.ms": "86400000",         "database.history.kafka.retention.bytes": "640073741824"     }

}

What is the captured database version and mode of depoyment?

oracle 19 c  onpremise mode

What behaviour do you expect?

debezium works as usually

What behaviour do you see?

debezium stop working

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

not tested

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

org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
        at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:67)
        at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:254)
        at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:62)
        at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:205)
        at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:172)
        at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:118)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'ALTER TABLE table_name SPLIT PARTITION table_name_CURRENT AT (TO_DATE('20240116040241', 'YYYYMMDDHH24MISS')) INTO (PARTITION table_name_20240116040241, PARTITION table_name_CURRENT) UPDATE INDEXES;'
mismatched input 'UPDATE' expecting {<EOF>, '/', ';'}
        at io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:43)
        at org.antlr.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41)
        at org.antlr.v4.runtime.Parser.notifyErrorListeners(Parser.java:543)
        at org.antlr.v4.runtime.DefaultErrorStrategy.reportInputMismatch(DefaultErrorStrategy.java:327)
        at org.antlr.v4.runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:139)
        at io.debezium.ddl.parser.oracle.generated.PlSqlParser.sql_script(PlSqlParser.java:2193)
        at io.debezium.connector.oracle.antlr.OracleDdlParser.parseTree(OracleDdlParser.java:73)
        at io.debezium.connector.oracle.antlr.OracleDdlParser.parseTree(OracleDdlParser.java:32)
        at io.debezium.antlr.AntlrDdlParser.parse(AntlrDdlParser.java:78)
        at io.debezium.connector.oracle.antlr.OracleDdlParser.parse(OracleDdlParser.java:68)
        at io.debezium.connector.oracle.OracleSchemaChangeEventEmitter.emitSchemaChangeEvent(OracleSchemaChangeEventEmitter.java:85)
        at io.debezium.pipeline.EventDispatcher.dispatchSchemaChangeEvent(EventDispatcher.java:396)
        at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.handleSchemaChange(AbstractLogMinerEventProcessor.java:702)
        at io.debezium.connector.oracle.logminer.processor.memory.MemoryLogMinerEventProcessor.handleSchemaChange(MemoryLogMinerEventProcessor.java:223)
        at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.processRow(AbstractLogMinerEventProcessor.java:331)
        at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.processResults(AbstractLogMinerEventProcessor.java:277)
        at io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor.process(AbstractLogMinerEventProcessor.java:207)
        at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:241)
        ... 9 more
Caused by: org.antlr.v4.runtime.InputMismatchException
        at org.antlr.v4.runtime.DefaultErrorStrategy.sync(DefaultErrorStrategy.java:270)
        at io.debezium.ddl.parser.oracle.generated.PlSqlParser.sql_script(PlSqlParser.java:2125)
   

How to reproduce the issue using our tutorial deployment?

split the table

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>