IBM Support

Defined two datasources to use two different JDBC drivers, but both datasources are using the same JDBC driver

Troubleshooting


Problem

If the different versions JDBC driver have the same classnames, then whichever classes are loaded first are used. Since JDBC provider classes are loaded by a WebSphere Application Server classloader, if you define JDBC providers that use different JDBC drivers of the same family (for example, both Oracle 10g and Oracle 11g thin driver), then which JDBC driver gets loaded is determined by which JDBC provider is processed first by the WebSphere Java™ Virtual Machine (JVM). For example, if you define one JDBC provider to use driver for Oracle 10g and another JDBC provider to use Oracle 11g, and define two datasource's, one using each JDBC provider. The SystemOut.log file will show that both datasources are using the same driver.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Classloader","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;8.5;8.0;7.0","Edition":"Base;Enterprise;Network Deployment","Line of Business":{"code":"LOB77","label":"Automation Platform"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}},{"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":" ","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"7.0;6.1;6.0","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Historical Number

55997;660;706

Document Information

Modified date:
03 March 2025

UID

swg21200379