Wednesday, 18 September 2013

JDBC driver still pointing to v9.5 JDBC driver, after DB2v10 upgrade, in Sysout logs

JDBC driver still pointing to v9.5 JDBC driver, after DB2v10 upgrade, in
Sysout logs

We recently migrated DB2v9.6 to v10.1 . Even though I created new JDBC
provider and the classpath is pointing to the v10 jar files in the Admin
console of WebSphere Application Server, still the logs are having the
JDBC driver number as 3.59.81 which is v9.6 JDBC provider model number
[9/18/13 9:00:03:378 GMT] 0000002b SystemOut O [AMT] [GWALogger]
[2013-09-18 09:00:03,378] [DEBUG] Setting up a new datasource [9/18/13
9:00:03:992 GMT] 0000002b PrivExAction W J2CA0144W: No mappingConfigAlias
found for ConnectionFactory or DataSource jdbc/isc_tools_cf_aamt_aamtdbDS.
[9/18/13 9:00:05:796 GMT] 0000002b InternalGener I DSRA8203I: Database
product name : DB2/AIX64 [9/18/13 9:00:05:815 GMT] 0000002b InternalGener
I DSRA8204I: Database product version : SQL10012 [9/18/13 9:00:05:818 GMT]
0000002b InternalGener I DSRA8205I: JDBC driver name : IBM DB2 JDBC
Universal Driver Architecture [9/18/13 9:00:05:821 GMT] 0000002b
InternalGener I DSRA8206I: JDBC driver version : 3.59.81 [9/18/13
9:00:05:825 GMT] 0000002b InternalDB2Un I DSRA8212I: DataStoreHelper name
is: com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper@7a647a64.
[9/18/13 9:00:05:830 GMT] 0000002b WSRdbDataSour I DSRA8208I: JDBC driver
type : 4
I guess it should have been changed to 3.65.77 ?

No comments:

Post a Comment