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

Debezium.text.ParsingException: DDL statement couldn't be parsed

XMLWordPrintable

    • Critical

      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 connector : vers 2.7.2

      What is the connector configuration?

      <Your answer>

      What is the captured database version and mode of deployment?

      Oracle 19.c

      What behavior do you see?

      Unable to move past the connector failure. Error log attached in this ticket
      Error ==>
      Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'alter table DNE4.ME_CARRIER_HISTORY\n add constraint CHECK_ME_CAR_HST_COMM_TYPE\n check (communication_type in('EDI','NON-EDI','API')) novalidate parallel;'\nextraneous input 'parallel' expecting {<EOF>, '/', 

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

      (Ideally, also verify with latest Alpha/Beta/CR version)

      2.7.2 Final

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

      (You might be asked later to provide DEBUG/TRACE level log)

      No. Error log attached in this ticket

       

        1. downloaded-logs-20240923-050207.csv
          144 kB
          Ravi Rai
        2. downloaded-logs-20240923-051026.json
          271 kB
          Ravi Rai
        3. Error_log.txt
          4 kB
          Ravi Rai

              vjuranek@redhat.com Vojtech Juranek
              ravirai.69@gmail.com Ravi Rai (Inactive)
              Christopher Bradford, Vojtech Juranek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: