Db2 – Check Java Driver Version in Clients from Server

db2javajdbc

I have a Db2 database that is being used by many applications in different servers. I want to check from the Db2 server if the Java driver used in the different client applications is up-to-date.

Is the any way to check the version of the java driver client from the Db2 server?
I have tried the following without success:

db2 list application show detail
db2 "SELECT *  FROM TABLE(MON_GET_CONNECTION(cast(NULL as bigint), -2)) AS t"

In the last command, the CLIENT_PRDID column could have some of this information, but it only shows: JCC04110 and I do not know what does it mean.

Best Answer

This page https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.admin.mon.doc/doc/r0001170.html describes the client_product_id monitor element thus

Use this element to identify the product and code version of the data server client. It is in the form PPPVVRRM, where:

PPP identifies the product. This is "SQL" for IBM® relational database products. VV identifies a 2-digit version number. RR identifies a 2-digit release number. M identifies a 1-character modification level (0-9 or A-Z).

comparing what CLIENT_PRDID shows

SELECT distinct CLIENT_PRDID FROM TABLE(MON_GET_CONNECTION(NULL, -2))

JCC04220

vs the jdbc type 4 driver version

java -cp $DB2_HOME/java/db2jcc4.jar com.ibm.db2.jcc.DB2Jcc -version

IBM Data Server Driver for JDBC and SQLJ 4.22.29

gets a close match for me. I can't say I know why the mod level is not set.

on a different system, looking at the type 2 driver, I get JCC03690 from CLIENT_PRDID but IBM DB2 JDBC Universal Driver Architecture 3.72.44 from java com.ibm.db2.jcc.DB2Jcc -version.. so it's maybe nearly of right...

Related Solutions

DB2 – Fixing Selects After Migrating from RHEL5 to RHEL6

To avoid the SQL0805N error, try binding the CLI packages (you need to be connected): db2 bind db2clipk.bnd blocking all sqlerror continue grant public. The bind file is in the bnd directory under your DB2 client installation. If you don't have enough permissions to bind packages your DBA will have to do it for you.

The database server version shows in the connect command feedback: DB2 z/OS 10.1.5. There is no patch to be applied; you need to bind appropriate packages in the database for clients to work. This is a standard procedure when upgrading clients, because each new version of client software comes with its own packages that need to be bound to the database, so your DBA should not have any problem with that. Alternatively, he (or she) will tell you what client version you must use (for which the packages would already be bound).

MySQL and Java – SQL Command Works in Workbench but Not from Java Program

You need to change java code to something like (for simplicity sake error handling and closing statements omitted)

 try {
    conn = ..... 
    conn.setAutoCommit(false);
    Statement s1 = conn.createStatement();
    s1.executeUpdate(/*first insert */);
    s1.executeUpdate(/*second insert */);
     // etc
    conn.commit();
  }

Side notes. 1) it's much better to use PreparedStatement if you executing the same query multiple times with different parameters. 2) make sure your catch block has conn.rollback() - you don't want to leave transaction open

Best Answer

Related Solutions

DB2 – Fixing Selects After Migrating from RHEL5 to RHEL6

MySQL and Java – SQL Command Works in Workbench but Not from Java Program

Related Question