Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-9397

Oracle DDL parser exception - DROP MATERIALIZED

XMLWordPrintable

      Hello,

      The connector throws an exception and stops after running a 'DROP MATERIALIZED VIEW LOG' query.

      What Debezium connector do you use and what version?

      2.7.4.Final

      What is the connector configuration?

      The connector is configured to include the table MY_SCHEMA.MY_TABLE

      What is the captured database version and mode of deployment?

      Version 19. On-premise

      What behavior do you expect?

      No exception

      What behavior do you see?

      Exception in the connector logs:

       

      Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed.
Please open a Jira issue with the statement 'DROP MATERIALIZED VIEW LOG ON MY_SCHEMA.MY_TABLE;' no viable alternative at input 'DROP MATERIALIZED'

       

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

      Yes

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

      The exception stack trace:

       

      Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'DROP MATERIALIZED VIEW LOG ON MY_SCHEMA.MY_TABLE;'
no viable alternative at input 'DROP MATERIALIZED'
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.reportNoViableAlternative(DefaultErrorStrategy.java:310)
at org.antlr.v4.runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:136)
at io.debezium.ddl.parser.oracle.generated.PlSqlParser.unit_statement(PlSqlParser.java:2905)
at io.debezium.ddl.parser.oracle.generated.PlSqlParser.sql_script(PlSqlParser.java:2137)
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:76)
at io.debezium.connector.oracle.antlr.OracleDdlParser.parse(OracleDdlParser.java:68)
at io.debezium.connector.oracle.OracleSchemaChangeEventEmitter.emitSchemaChangeEvent(OracleSchemaChangeEventEmitter.java:104)
at io.debezium.pipeline.EventDispatcher.dispatchSchemaChangeEvent(EventDispatcher.java:388)
at io.debezium.connector.oracle.xstream.LcrEventHandler.dispatchSchemaChangeEvent(LcrEventHandler.java:262)
... 12 more
Caused by: org.antlr.v4.runtime.NoViableAltException
at org.antlr.v4.runtime.atn.ParserATNSimulator.noViableAlt(ParserATNSimulator.java:2028)
at org.antlr.v4.runtime.atn.ParserATNSimulator.execATN(ParserATNSimulator.java:467)
at org.antlr.v4.runtime.atn.ParserATNSimulator.adaptivePredict(ParserATNSimulator.java:393)
at io.debezium.ddl.parser.oracle.generated.PlSqlParser.unit_statement(PlSqlParser.java:2438)
... 21 more

       

      How to reproduce the issue using our tutorial deployment?

      1. Create a MATERILIZED VIEW LOG on a database table that the connector uses
      2. Run DROP MATERILIZED VIEW LOG on the same table
      3. Check connector logs

              ccranfor@redhat.com Chris Cranford
              andrejs2025 Andrejs Jermakovics
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: