My Oracle Support Banner

"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 12.2.1.4.0 to 12.2.1.4.200123 [Release 12c]
Microsoft Windows x64 (64-bit)

Symptoms

When testing a database dataserver using a 3rd party JDBC driver (like IBM BD2, Teradata, PostgreSql, etc) on an Oracle Data Integrator (ODI) 12.2.1.4 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:

oracle.odi.runtime.agent.invocation.InvocationException: oracle.odi.core.exception.OdiRuntimeException: java.lang.RuntimeException: java.lang.IllegalArgumentException: Could not load JDBC driver class [com.ibm.as400.access.AS400JDBCDriver]
  at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:475)
  at oracle.odi.runtime.agent.invocation.support.InternalRemoteRuntimeAgentInvoker.invoke(InternalRemoteRuntimeAgentInvoker.java:162)
  at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:961) at java.lang.Thread.run(Thread.java:748)
  ...

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

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.