JDBC Driver Versions

[drudini]

We have installed DB2UDB 8.2 on a windows 2003 server. How can I
confirm the version of the JDBC driver that would have been installed
with this? I wasn;t sure if the JBDC driver would have a different
version/build then the DB version itself.

Thanks,
Bob Cook

[joe.weinstein]

drudini wrote:

We have installed DB2UDB 8.2 on a windows 2003 server. How can I
confirm the version of the JDBC driver that would have been installed
with this? I wasn;t sure if the JBDC driver would have a different
version/build then the DB version itself.

Thanks,
Bob Cook

Versions of JDBC drivers may often evolve independently
of the DBMS. JDBC offers one standard call to determine
the driver version:

DatabaseMetaData.getDriverVersion()

You have to make a valid connection in order to make this
call. Otherwise, if you're good at decompiling, you can usually
find the static final string that determines this.

Joe Weinstein at BEA Systems

[Bernd Hohmann]

jo***********@gmail.com wrote:

DatabaseMetaData.getDriverVersion()

You have to make a valid connection in order to make this
call. Otherwise, if you're good at decompiling, you can usually
find the static final string that determines this.

I don't know if the output of getDriverVersion() is updated on each
fixpack (I guess it isn't). The best way to synchronize the driver on
the client is to deploy it with a batch after each fixpack.

From our experiences since 5.x/6.x, we're comparing filesize/date and
then the MD5 checksum. If they don't match, the driver is copied to the
client before the database connection is established.

Bernd

[Jan M. Nelken]

drudini wrote:

We have installed DB2UDB 8.2 on a windows 2003 server. How can I
confirm the version of the JDBC driver that would have been installed
with this? I wasn;t sure if the JBDC driver would have a different
version/build then the DB version itself.

Thanks,
Bob Cook

"db2jcc -version" will tell you the JCC driver version. "db2jcc -configuration"
will tell you everything you ever wanted to know about your configuration.

Jan M. Nelken