IBM Support

DB2 Universal JDBC/SQLJ driver on HP-UX - "encoding not supported"

Question & Answer


Question

When using the DB2® UDB v8 Universal JDBC/SQLJ driver with an application on HP connecting to an HP-UX DB2 UDB server, you will receive an "encoding not supported" error when the database has been created using the default codepage. Example 1: JDBC application example: try { Class.forName("com.ibm.db2.jcc.DB2Driver"); } catch(java.lang.ClassNotFoundException e) { .... } try { conn = DriverManager.getConnection("jdbc:db2:userdb", "test", "test"); ... } ... You may receive the following error: com.ibm.db2.jcc.b.DisconnectException: encoding not supported!! .... at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:135) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:172) .... Example 2: SQLJ applications could encounter a similar error at runtime or during developement using SQLJ utilities (db2sqljcustomize, etc. ). For example: [java] [ibm][db2][jcc][sqlj] encoding not supported!!

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Programming Interface - JDBC - Type 2","Platform":[{"code":"PF010","label":"HP-UX"}],"Version":"8","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
04 June 2026

UID

swg21114928

Page Feedback