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

Oracle SQL parsing error when collation used

XMLWordPrintable

    • False
    • None
    • False

      What Debezium connector do you use and what version?

      io.debezium.connector.oracle.OracleConnector 1.9.5

      What is the connector configuration?

          connector.class=io.debezium.connector.oracle.OracleConnector
          database.hostname=ORAT03.mydomain.local
          database.port=5500
          database.user=c##debezium
          database.password=xxxxx
          database.dbname=MYDB03
          database.server.name=MY_DB_NAME
          tasks.max=1
          database.pdb.name=MY_DB_NAME
          database.history.kafka.bootstrap.servers=kafka-broker:9092
          database.history.kafka.topic=schema-changes.oracle
          decimal.handling.mode=string

      What is the captured database version and mode of depoyment?

      On-premises Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
      Version 19.15.0.0.0

      What behaviour do you expect?

      Log miner event handled without error and connector not stopping down.

      What behaviour do you see?

      Log miner event handled with error and connector stops down.

      Also should that event be handled at all since it is an event on table TOKENSTORE which is not one of the tables identified as one of the captured tables in the Snapshot step 2?

      If I specify the list of tables I'm interested in with table.include.list then this error doesn't occur and the connector doesn't stop down.

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

      Didn't try latest version

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

      Yes

              anmohant Anisha Mohanty
              jaintir1 Raj Jaintilal (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: