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

Debezium Crash on U DB2 LUW Update

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.4.0.CR1
    • 3.2.0.Beta1
    • db2-connector
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      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?

      3.2

      What is the connector configuration?

      { "connector.class": "io.debezium.connector.db2.Db2Connector", "database.hostname": "db2", "database.port": "50000", "database.user": "DB2INST1", "database.password": "admin", "database.dbname": "BNKNG", "topic.prefix": "cdc", "table.include.list": "DB2INST1.CUSTOMERS, DB2INST1.ORDERS, DB2INST1.PRODUCTS, DB2INST1.PRODUCTS_ON_HAND", "auto.create": true, "schema.history.internal.kafka.bootstrap.servers": "", "schema.history.internal.consumer.security.protocol": "SASL_SSL", "schema.history.internal.consumer.ssl.endpoint.identification.algorithm": "https", "schema.history.internal.consumer.sasl.mechanism": "PLAIN", "schema.history.internal.consumer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username= password= "schema.history.internal.producer.security.protocol": "SASL_SSL", "schema.history.internal.producer.ssl.endpoint.identification.algorithm": "https", "schema.history.internal.producer.sasl.mechanism": "PLAIN", "schema.history.internal.producer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username= password= "schema.history.internal.kafka.topic": "debezium.schemahistory" }

      What is the captured database version and mode of deployment?

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

      DB2 LUW, in a container

      What behavior do you expect?

      When db2 replication is set to use a single update row (from IBMSNAP_REGISTER CHG_UPD_TO_DEL_INS = N), an update should not crash the connector task, but should produce an update event, but not have a before record.

      What behavior do you see?

      <Your answer>

      Do you see the same behaviour using the latest released 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>

              Unassigned Unassigned
              mhejnas_converge Matt Hejnas
              Matt Hejnas
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: