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

DB2 Signaling creates watermarking in the wrong schema

XMLWordPrintable

    • Moderate

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      DB2 3.0.7

      What is the connector configuration?

      spec:
          class: io.debezium.connector.db2.Db2Connector
          config:
              database.hostname: ******
              tasks.max: 1
              database.port: 50010
              database.user: db2usr1
              database.password: ****
              database.dbname: fabric
              database.cdcschema: ASNCDC
              table.include.list: DB2INST1.PRODUCTS,DB2INST1.ORDERS,DB2INST1.ORDERS2
              schema.history.internal.kafka.boostrap.servers: "kafka-cluster-kafka-bootstrap:9092"
              schema.history.internal.kafka.topic: "schemahistory.iceberg"
              internal.advanced.metrics.enable: true
              signal.data.collection: DB2INST1.DEBEZIUM_SIGNAL

      What is the captured database version and mode of deployment?

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

      On prem DB2, EKS running strimzi

      What behavior do you expect?

      Use signaling table specified in the connector configuration

      What behavior do you see?

      Uses the signaling table based on the logged in user. e.g. DB2USR1.DEBEZIUM_SIGNAL 

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

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

      Yes

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

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

      Requested incremental snapshot of data collections '[DB2INST1.ORDERS]'

       

      Db2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=Db2USER1.DEBEZIUM_SIGNAL, DRIVER=4.26.14

      How to reproduce the issue using our tutorial deployment?

      Change the logged in user to not be DB2INST1

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      Incremental Snapshots

      Implementation ideas (optional)

      Respect the configuration

      Current Workaround

      Create a signaling table in the schema matching the username instead of in the configuration. it seems as if the watermarking code and the signal reading code are determining the table names in a different way

              rh-ee-mvitale Mario Fiore Vitale
              ikikomonkey Kyle DePace (Inactive)
              Chris Cranford
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: