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

XMLType using non-Binary storage throws parser failure

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Important

      Bug report

      What Debezium connector do you use and what version?

      Debezium Oracle 2.7

      What is the connector configuration?

      {
        "name": "t24_1table",
        "config":

      {     "metrics.jmx.enable": "false",     "schema.history.internal.kafka.bootstrap.servers": "kafka.data-platform.svc.cluster.local:9092",     "schema.history.internal.kafka.topic": "schema-changes.t24-1table",     "name": "t24_1table",     "connector.class": "io.debezium.connector.oracle.OracleConnector",     "tasks.max": "1",     "topic.prefix": "t24_1table",     "database.hostname": "*****",     "database.port": "*****",     "database.user": "*****",     "database.password": "*****",     "database.dbname": "*****",     "snapshot.mode": "no_data",     "log.mining.strategy": "redo_log_catalog",     "snapshot.mode.configuration.based.snapshot.data": "false",     "snapshot.mode.configuration.based.snapshot.schema": "false",     "snapshot.mode.configuration.based.start.stream": "false",     "lob.enabled": "true",     "schema.history.internal.store.only.captured.tables.ddl": "true",     "topic.naming.strategy": "io.debezium.schema.SchemaTopicNamingStrategy",     "table.include.list": "T24.FBNK_CUSTOMER",     "include.schema.changes": "false"   }

      }

      What is the captured database version and mode of deployment?

      On-Prem Oracle 19c

      What behavior do you expect?

      I should get the captured logs in the kafka topic for this table without any errors in the connector

      What behavior do you see?

      I get this error once there's an update statement is performed by the application.

      ERROR [t24_1table|task-0] Mining session stopped due to error. (io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource:262)
      io.debezium.text.ParsingException: Parsing failed for SQL: 'update "T24"."FBNK_CUSTOMER" a set a."XMLRECORD" = XMLType(:1) where a."RECID" = '123';'

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

      Didn't try the latest releases

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

      nope

      How to reproduce the issue using our tutorial deployment?

      It's an application behaviour to update or insert the data in the table and I am not sure how the update statement exactly look like. But it seems to me it's like update "T24"."FBNK_CUSTOMER" a set a."XMLRECORD" = XMLType(:1) where a."RECID" = '123';

      and pass an xml in the parameter.

       

        1. config.json
          1 kB
          Muhammad ElOkda
        2. ddl.sql
          0.4 kB
          Muhammad ElOkda
        3. error.json
          3 kB
          Muhammad ElOkda

              ccranfor@redhat.com Chris Cranford
              m.elokda@scbank.com.eg Muhammad ElOkda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: