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

Unparseable DDL statement


      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 1.9.5.Final-redhat-00001

      What is the connector configuration?

       database.dbname:                           BOSCS19
          database.history.kafka.bootstrap.servers:  pcl-tracking-cluster-kafka-bootstrap:9092
          database.history.kafka.topic:              schema-changes.cdc.debezium.tt2-event
          database.hostname:                         t-ttnv-scan.rete.testposte
          database.password:                         ${secrets:tt2-event/debezium-connector-tt2-event-db:password}
          database.port:                             1521
          database.server.name:                      cdc.debezium.tt2-event
          database.user:                             ${secrets:tt2-event/debezium-connector-tt2-event-db:username}
          key.converter:                             org.apache.kafka.connect.json.JsonConverter
          key.converter.schemas.enable:              false
          table.include.list:                        DB_TRACK_OWNER.TRACK_EVO_TRACES
          value.converter:                           org.apache.kafka.connect.json.JsonConverter
          value.converter.schemas.enable:            false    

      What is the captured database version and mode of depoyment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      <Your answer>

      What behaviour do you expect?

      <Your answer>

      What behaviour do you see?

      Multiple parsing errors
      io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'alter table PK_CNT_GIORNI_TIPI_INC split partition PMAX at (TO_DATE('1410202215','DDMMYYYYHH24'))
           INTO (PARTITION P2022101414, PARTITION PMAX);

      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>

            anmohant Anisha Mohanty
            saiello@redhat.com Simone Aiello (Inactive)
            Maurizio Romani (Inactive)
            1 Vote for this issue
            5 Start watching this issue