Contribute in GitHub:
Open doc issue|Edit online
JDBC Connector
Use the workaround and solutions to resolve issues related to JDBC connectors.
- Nullpointer exception
In case you face a Nullpointer exception while using Custom Prepared Statements, try to resolve the issue with instructions provided here. - COM.ibm.db2.jdbc.DB2Exception: CLI0616E Error opening socket. SQLSTATE=08S01
A server service named DB2® JDBC Applet Server must be running on the Windows system where the DB2 server is running. If The DB2 JDBC Applet Server service is not running you will get this message. - CLI0616E Error opening socket
The remote DB2 server is not configured for DB2 net driver communications. Refer to the FAQ that has more information on connecting to a DB2 server. - java.sql.SQLException: ORA-01830: date format picture ends before converting entire input string
There are a number of ways to resolve this issue. Read the instructions provided here to have a better understanding on date format related errors. - Handling of CLOB/BLOB (Character/Binary large object)
Handle the attributes of CLOB/BLOB type on input with the instructions provided here. - Disabling Prepared Statement results in an exception
Disabling Prepared Statement can result in an exception for queries that exceed the maximum length value. - Transferring BLOB data in an Oracle database
Use ojdbc14.jar instead of using classes12.jar when using the JDBC Connector to transfer BLOB data from one table to another table in an Oracle database. - InitConnectors: com.ibm.db2.jcc.a.SqlException
The exception means that the version of the IBM® Universal JDBC driver in use is not licensed for connectivity to QDB2/<OS> databases. Use the workaround provided here to work upon this exception.