"Could not load JDBC driver class" Error when Using a Standalone/Collocated Agent with 3rd Party JDBC Drivers
(Doc ID 2628363.1)
Last updated on MAY 15, 2020
Applies to:Oracle Data Integrator - Version 18.104.22.168.0 to 22.214.171.124.200123 [Release 12c]
Microsoft Windows x64 (64-bit)
When testing a database dataserver using a 3rd party JDBC driver (like IBM BD2, Teradata, PostgreSql, etc) on an Oracle Data Integrator (ODI) 126.96.36.199 Standalone/Collocated Agent, an error occurs related to the loading of the JDBC driver. For example, the following error occur when using the IBM DB/2 driver:
The connection is successful when using "Local (No agent)". The JDBC driver is placed correctly in $ODI_Home/user_projects/domains/<DOMAIN_NAME>/lib directory, as per Document 423914.1 - How To Set Up Database Connections for Third Party JDBC Drivers Such as Microsoft SQL Server, Sybase, PostgreSQL, etc
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document