Wednesday, 25 April 2012

More on DB2 UDB JDBC drivers ...

This following yesterday's post, I've just gone through the process of inferring the version/type of JDBC driver that I'm using: -

$ ls -al

total 3336
drwxr-x---  2 wasadmin wasgrp    4096 Dec  8  2010 .
drwxr-x--- 40 wasadmin wasgrp    4096 Jul 25  2011 ..
-rwxr-x---  1 wasadmin wasgrp 3395609 Dec  8  2010 db2jcc4.jar
-rwxr-x---  1 wasadmin wasgrp    1015 Dec  8  2010 db2jcc_license_cu.jar

$ . /opt/IBM/WebSphere/wp_profile/bin/setupCmdLine.sh
$ java -version

java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr9fp2ifix-20110913_02(SR9 FP2+IV03622+IZ99243))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr9-20110912_90359 (JIT enabled, AOT enabled)
J9VM - 20110912_090359
JIT  - r9_20101028_17488ifx31
GC   - 20101027_AA)
JCL  - 20110727_04

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

IBM Data Server Driver for JDBC and SQLJ 4.8.87

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...