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

Oracle connector fails when using database.tablename.case.insensitive=true

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.5.0.Beta2
    • None
    • oracle-connector
    • None

      The option database.tablename.case.insensitive was added in DBZ-954 so that Oracle 11g would work with the connector. Both the configuration class and documentation state that this setting should only be set to true when using Oracle 11g; however, we've had several reports where users have set this on Oracle 12+ environments and experienced varied inconsistent behavior.

      See https://gitter.im/debezium/user?at=6034b854e634904e60ba19a4

      In the above discussion, an Oracle 12 user had set this option to true which caused a query that checks for a table's supplemental logging to fail because the generated SQL was:

      WHERE owner = 'SCOTT' and table_name = 'mtl_material_transactions'

      rather than

      WHERE owner = 'SCOTT' and table_name = 'MTL_MATERIAL_TRANSACTIONS'

      Due to how Oracle 12+ would match the text string, the inconsistent case in the value led to no results being returned & an error being shown to the user despite the fact they had accurately configured the supplemental logging for the table.

              ccranfor@redhat.com Chris Cranford
              ccranfor@redhat.com Chris Cranford
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: