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

Debezium Db2 connector fails with tables using BOOLEAN type

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.3.0.Final
    • None
    • db2-connector
    • None
    • False
    • False
    • Undefined
    • Hide

      Create a table with at least 1 column of type BOOLEAN on Db2 11.5.0.0 or 11.5.0.0, enable ASN replication using the tooling provided with the Debezium Db2 connector and the moment a change is made to the table the ASN capture fails.

      Show
      Create a table with at least 1 column of type BOOLEAN on Db2 11.5.0.0 or 11.5.0.0, enable ASN replication using the tooling provided with the Debezium Db2 connector and the moment a change is made to the table the ASN capture fails.

      A table with a column of type BOOLEAN can be successfully snapshotted, but streaming changes will fail killing the ASN capture server. No changes will be propagated to Kafka.

      We are investigating whether this is a bug in the Db2 ASN capture server or a problem on our side.

            [DBZ-2587] Debezium Db2 connector fails with tables using BOOLEAN type

            Released

            Jiri Pechanec added a comment - Released

            Ok, thanks. Could you send a PR for adding a warning to the docs then for the time being?

            Gunnar Morling added a comment - Ok, thanks. Could you send a PR for adding a warning to the docs then for the time being?

            I opened a support ticket with IBM.

            Luis Garcés-Erice (Inactive) added a comment - I opened a support ticket with IBM.

            It's looking more and more like the problem is with Db2 ASN itself, not Debezium. If that is the case, it would probably be a good idea to have that stated somewhere to avoid surprises.

            I see, and yes, agreed in this case. A PR will be welcomed.

            Gunnar Morling added a comment - It's looking more and more like the problem is with Db2 ASN itself, not Debezium. If that is the case, it would probably be a good idea to have that stated somewhere to avoid surprises. I see, and yes, agreed in this case. A PR will be welcomed.

            If we can create a small scenario which shows Db2 ASN fails when capturing changes from a table

            with a BOOLEAN column, we should raise a trouble ticket with IBM.

            Sean Rooney (Inactive) added a comment - If we can create a small scenario which shows Db2 ASN fails when capturing changes from a table with a BOOLEAN column, we should raise a trouble ticket with IBM.

            A fix (if needed within Debezium) will be welcomed very much though 

            Well, that's the thing. It's looking more and more like the problem is with Db2 ASN itself, not Debezium. If that is the case, it would probably be a good idea to have that stated somewhere to avoid surprises.

            Luis Garcés-Erice (Inactive) added a comment - A fix (if needed within Debezium) will be welcomed very much though  Well, that's the thing. It's looking more and more like the problem is with Db2 ASN itself, not Debezium. If that is the case, it would probably be a good idea to have that stated somewhere to avoid surprises.

            Hey lga, we don't typically document bugs, so I don't think it's needed. A fix (if needed within Debezium) will be welcomed very much though

            Gunnar Morling added a comment - Hey lga , we don't typically document bugs, so I don't think it's needed. A fix (if needed within Debezium) will be welcomed very much though

            gunnar.morling should a quick update of the Db2 connector documentation be in order, at least until we find what the issue is?

            Luis Garcés-Erice (Inactive) added a comment - gunnar.morling should a quick update of the Db2 connector documentation be in order, at least until we find what the issue is?

              lga@zurich.ibm.com Luis Garcés-Erice (Inactive)
              lga@zurich.ibm.com Luis Garcés-Erice (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: