IBM Support occurs when accessing DBCS data from a JDBC application running under JRE 1.8+



An application using the IBM Data Server Driver for JDBC and SQLJ accesses a database that uses double byte character set encoding for character data (such as CCSID 1399 - Japanese). When running under JRE 1.8 or above, the application receives an SQL Exception with the message "Caught" and ERRORCODE=-4220 on querying character data..


An exception is thrown similar to this: [jcc][t4][1065][12306][XXX.XXX.XXX] Caught See attached Throwable for details. ERRORCODE=-4220, SQLSTATE=null
Caused by: java.nio.charset.MalformedInputException: Input length = XXX

The same application works without any exceptions under JRE 1.7 or lower.


IBM Data Server Driver for JDBC and SQLJ relies on the Java runtime for byte to character conversions. The error occurs due to presence of specific byte sequences in the character data that were accepted by Java character converters in JRE 1.7 and lower but are considered invalid and rejected in JRE 1.8 with a


Java Runtime Environment 1.8 or above

Diagnosing The Problem

You can use the HEX function to find out the byte values for data in a character column:

For example, to find out the byte values in column COL1 in table TAB1, run: 

SELECT HEX(col1) FROM tab1

With respect to the designated character set encoding / CCSID, this may help identify the invalid byte sequences that need to be rectified.

Resolving The Problem

The solution to the problem is to identify and correct the invalid data.

The following workaround may be used to maintain application continuity until the invalid data is fixed:

  • IBM Data Server Driver for JDBC and SQLJ versions 3.70, 4.20 and above support JRE 1.8. Confirm that the version of the IBM Data Server Driver for JDBC and SQLJ used by the application supports JRE 1.8.
  • Set the driver configuration property db2.jcc.charsetDecoderEncoder=3

    With this property set, the driver instructs the Java character converters to use a replacement (dummy) character in the decoding output of an invalid sequence of bytes instead of throwing the exception.

Another option is to continue running the application under JRE 1.7 or lower to avoid the error.

[{"Product":{"code":"SSEPDU","label":"Db2 Connect"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;10.1;10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018