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

Journal access for tables with non-ASCII names

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.4.0.Beta1
    • 3.3.1.Final
    • ibmi-connector
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Important

      Bug report

      I am setting up the Debezium connector for DB2 on IBMi for a client.

      We have had some success but are getting an error when trying to include a table with non-ASCII characters in the name.

      When I include the table "ÖTABL" I get an exception:

      Caused by: java.lang.IllegalStateException: Journal not found for ÖTABL error File @TABL in library ... not found.
      I have confirmed that the table exists and is correctly journalled.

      I think the problem is in the way the JournalInfoRetrieval calls the program QDBRTVFD.

      The JournalInfoRetriever uses a JT400 class AS400Text that seems to use default CCSID 37 (US EBCDIC) whereas we are using 278 (Swedish EBCDIC).

      https://github.com/jhc-systems/debezium-connector-ibmi/blob/main/journal-parsing/src/main/java/com/fnz/db2/journal/retrieve/JournalInfoRetrieval.java#L48

      Changing the parameters "from.ccsid" and "to.ccsid" has no effect.

      What Debezium connector do you use and what version?

      Debezium connector for DB2 on iSeries, version 3.3.1-Final

      What is the connector configuration?

      What is the captured database version and mode of deployment?

      DB2 is deployed on prem

      Connector is deployed in Confluent Connect on an on-prem RedHat OpenShift cluster

      What behavior do you expect?

      The table "ÖTABL" should be handled by the connector

      What behavior do you see?

      Tables with an "Ö" in it fail to access the journal (see above). The table is accessible (as ÖTABL) but the journal is referenced as @TABL

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

      We have seen this in versions 3.1.x to 3.3.1-Final

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

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

      Can be provided

      How to reproduce the issue using our tutorial deployment?

      Set up a table called ÖTABL, you may need to have a Swedish EBCDIC DB2 implementation available. Start the connector.

              Unassigned Unassigned
              martin.holt@callistaenterprise.se Martin Holt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: