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

When monitoring tables, DB2 encountered an unsupported type, and the asncap service connected to DB2 was disconnected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • None
    • 1.9.5.Final
    • db2-connector
    • None
    • False
    • 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

      I have a watch like this:
      CREATE TABLE "DBZ "."NORMAL_TYPE1" (
      "ID" INTEGER NOT NULL ,
      "FIRST_NAME" VARCHAR(255 OCTETS) ,
      "T_TIMESTAMP" TIMESTAMP ,
      "T_BIGINT" BIGINT ,
      "T_TIME" TIME ,
      "T_DATE" DATE ,
      "T_BOOLEAN" BOOLEAN ,
      PRIMARY KEY ("ID"));

      I am now facing the problem of "asncap" service of DB2. I am going to monitor a table of DB2. After opening CDC, when I add a piece of data to this table, I check the mapping table under asncdc. When I monitor the data I add, I find that it is empty. When I use the "DB2 list applications" command to view the service, I find that "asncap" has been disconnected. After testing, the problem of disconnection is caused by the "Boolean" type, I know that although the official document of debezium says that it only supports snapshot data of "Boolean" type and does not support change replication, I have a question. Can't I skip the unsupported types? Why should I disconnect the "asncap" service? In this case, this monitoring can't continue. DB2 can skip the unsupported types like Oracle or SQL server, but my service is running normally

      Finally, I have a question about how to generate the monitoring log of the service after I start the asncap service. In this case, if there is a problem with the proxy service, I can check the problem through the log

              Unassigned Unassigned
              ryan-0526 逸南 丁 (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: