# "Could not load JDBC driver class” Error in Oracle Data Integrator when working with an agent **URL:** \ **Category:** CData Drivers\ **Tags:** discussion, driver, jdbc, odi\ **Created:** [April 24, 2024, 6:12am UTC](https://community.cdata.com/t/could-not-load-jdbc-driver-class-error-in-oracle-data-integrator-when-working-with-an-agent/699 "2024-04-24T06:12:21Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ekanshd](https://avatars.discourse-cdn.com/v4/letter/e/76d3ee/32.png) [@ekanshd](https://community.cdata.com/u/ekanshd)\ **Post date:** [April 24, 2024, 6:12am UTC](https://community.cdata.com/t/could-not-load-jdbc-driver-class-error-in-oracle-data-integrator-when-working-with-an-agent/699/1 "2024-04-24T06:12:21Z")
In this article, we will walk through how to resolve an error received in Oracle Data Integrator (ODI) when trying to connect with 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.\]** This error message indicates that the Driver is not accessible to ODI and therefore, ODI could not load it. The steps to resolve this error are as follows: Place the JAR and LIC files of the JDBC Driver within ODI’s userlib directory if you’re working without the agent. The location of the userlib directory is dependent on OS. UNIX system: $HOME/.odi/oracledi/userlib Windows systems: %APPDATA%\odi\oracledi\userlib Please note that if we’re working with an oracle agent in ODI then we need to place the .jar and .lic files in both the locations which are as follows: UNIX system: **$HOME/.odi/oracledi/userlib.** and **$ODI\_HOME/odi/agent/lib** Windows system:  **%APPDATA%\Roaming\odi\oracledi\userlib** and  **%APPDATA%\Roaming\odi\agent\lib** By doing this, ODI will read the jar file successfully and we’ll not face this error. After following the above steps, please make sure to restart ODI. Restarting ODI is necessary for the changes to be implemented. After this, please follow our knowledge base article to configure our JDBC driver in ODI, the steps and functionality will be consistent with any data source in terms of adding the driver JAR and using it within ODI. [ETL Azure Synapse in Oracle Data Integrator (cdata.com)](https://www.cdata.com/kb/tech/azuresynapse-jdbc-odi.rst) If you’re still running into any errors, please reach out to us at [support@cdata.com](mailto:support@cdata.com). ---
**Author:** ![Luçjano\_Capo](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/lu%C3%A7jano_capo/32/1638_2.png) [@Luçjano\_Capo](https://community.cdata.com/u/Lu%C3%A7jano_Capo)\ **Post date:** [May 16, 2024, 10:11am UTC](https://community.cdata.com/t/could-not-load-jdbc-driver-class-error-in-oracle-data-integrator-when-working-with-an-agent/699/2 "2024-05-16T10:11:19Z")
Hi @ekanshd , Thank you for the information provided! I acknowledge the importance of this information. Could we consider publishing it as a  **Knowledge Base**  article on our CData Community rather than a question? I believe it would be more beneficial as part of our  **Troubleshooting**  section within the  **Editions**  category. By creating a dedicated  **Knowledge Base**  article, we can provide more clarity and address any uncertainties our customers may have. ---
**Author:** ![ekanshd](https://avatars.discourse-cdn.com/v4/letter/e/76d3ee/32.png) [@ekanshd](https://community.cdata.com/u/ekanshd)\ **Post date:** [May 30, 2024, 6:13am UTC](https://community.cdata.com/t/could-not-load-jdbc-driver-class-error-in-oracle-data-integrator-when-working-with-an-agent/699/3 "2024-05-30T06:13:43Z")
Hi @Luçjano_Capo , Thanks for your concern. I have already raised a website project to update the necessary changes in the existing KB article that we have, and the changes are successfully implemented in the KB article. You can also have a look into it here: [ETL Azure Synapse in Oracle Data Integrator (cdata.com)](https://www.cdata.com/kb/tech/azuresynapse-jdbc-odi.rst) Also, the changes are done in all the KBs of every data source that can be integrated with ODI to perform ETL. ---
**Author:** ![Luçjano\_Capo](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/lu%C3%A7jano_capo/32/1638_2.png) [@Luçjano\_Capo](https://community.cdata.com/u/Lu%C3%A7jano_Capo)\ **Post date:** [May 30, 2024, 10:06am UTC](https://community.cdata.com/t/could-not-load-jdbc-driver-class-error-in-oracle-data-integrator-when-working-with-an-agent/699/4 "2024-05-30T10:06:03Z")
Thank you for the update. Great work @ekanshd !