“Could not load JDBC driver class” Error in Oracle Data Integrator

  • 8 November 2023
  • 0 replies
  • 344 views

Userlevel 3
Badge

In this article, we will walk through how to resolve an error received in Oracle Data Integrator (ODI) when trying to connect one of our JDBC Drivers. Below is an example of the error, specifically the first line in the Exception Stack Trace. 


java.lang.RuntimeException: java.lang.IllegalArgumentException: Could not load JDBC driver class [cdata.jdbc.<Driver Name>] 

 

This error message indicates that the Driver is not accessible to ODI and therefore, ODI could not load it. 

 

There are a few steps you can take to resolve this error. 

  1. Place the JAR and LIC files of the JDBC Driver within ODI’s userlib directory. The location of the userlib directory is dependent on OS.  

 

UNIX system: $HOME/.odi/oracledi/userlib 

Windows systems: %APPDATA%\odi\oracledi\userlib 

 

This can also be seen within Oracle’s documentation - https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.3/oding/configuring-oracle-data-integrator-studio.html#GUID-8005F6A0-2EB7-41B9-A6F6-749BFE67DC6E 

 

  1. Verify the user running ODI is also the user who placed the JDBC Driver in the ODI directory, as %APPDATA% and $HOME are specific to a user. We want to ensure the appropriate user loading the driver within ODI has the JAR and LIC files at the correct location. 

 

  1. If the previous two steps have been followed, then please make sure to restart ODI. Restarting ODI is necessary for the changes to be implemented. 

 

After following the steps outlined in this article, please follow the link below to a Knowledge Base article walking through how to connect to your data within ODI. Although this article is specific to Workday, outside of the configuration to make the data connection, the steps and functionality will be consistent with any data source in terms of adding the driver JAR and using it within ODI. 

 

https://www.cdata.com/kb/tech/workday-jdbc-odi.rst 

 

If you’re still running into any errors, please reach out to us at support@cdata.com


This topic has been closed for comments