By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,313 Members | 2,798 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,313 IT Pros & Developers. It's quick & easy.

DB2 v 8.1 universal JDBC Driver Weird behavior in WSAD 5.1.x and WAS 5.0.2

P: n/a
Hi,

I am configuring the same DB2 v8.1 JDBC universal driver (db2jcc.jar
and db2jcc_license_cisuz.jar) from DB2 SP5 fix pack under WSAD 5.1.x
environment and WebSphere application Server 5.0.2 on Windows 2000
machines. I configured a connection pool data source using type 4 for
a local test environment in WSAD 5.1.x, and a connection pool data
source on the WebSphere Server too. Both data sources are accessing
the same database.

The weird behaviour I have noticed:

In the WSAD 5.1.x environment, the log shows the JDBC driver version
is 1.9.23 as below:

.... WSRdbDataSour u Database version is
SQL08013
.... b509899 WSRdbDataSour u JDBC Driver version is
1.9.23

But on the WebSphere app server, the JDBC driver version is 1.3.71 as
below:

.... WSRdbDataSour u Database version is
SQL08010
.... b509899 WSRdbDataSour u JDBC Driver version is
1.3.71

I had configured both data source's JDBC providers to use the same
JDBC driver files I have list above. But somehow the data source on
the WebSphere server still thinks it's using an old version of the
univresal JDBC driver. The net result is that the .getString() method
on a CLOB column fails with the following error:

com.ibm.db2.jcc.b.SqlException: The length method on locator-based,
mixed character set Clob objects is not supported.

Any idea on what it means? because the db is not UTF-8?

But the same code works happily in the WSAB 5.1.x test environment.

The version 1.3.71 JDBC universal driver comes from DB2 V81. SP1, it
works fine except it does not work on the LOBs with those
get/setString on CLOBs and set/GetBytes on BLOBs. That problem is
consistent with WSAD 5.1.x, i.e. the LOBs do not work under the 1.3.71
version of universal JDBC driver. But it does work after I upgraded it
to 1.9.23 driver.

Any advice why I can not make the WebSphere app server to recognize
the newer version of the JDBC universal driver? What is the possible
cuase of the above error meesgae (i.e. com.ibm.db2.jcc.b.SqlException:
The length method on locator-based, mixed character set Clob objects
is not supported. )
Your help would be greatly appreciated.
Thanks.
Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.