Driver not found error using tnsnames like URL

Applies to: Denodo 8.0 , Denodo 7.0 , Denodo 6.0 , Denodo 5.5 , Denodo 5.0
Last modified on: 29 May 2020
Tags: Error handling JDBC data sources Oracle

Download document

You can translate the document:

Content

If encountering a “driver not found” error when trying to connect to a data source, you should first check that the proper driver exists in the correct jdbc driver location. Depending on the version that you use, you might need to check different locations.

Denodo 8.0

  • The recommended way is to navigate via the Administration Tool to File > Extension Management > Libraries and check if the driver was uploaded there. If you cannot find it here, you can simply upload it graphically instead of copying it manually. Note: The JDBC drivers included in the product distribution are not listed there and do not need to be uploaded.
  • The other option is to check if you can find the driver in one of these locations:
  • <DENODO_HOME>\lib\extensions\jdbc-drivers 
  • This location is for the adapters that have the drivers already included in the product distribution and they should usually not be changed manually.
  • <DENODO_HOME>\lib\extensions\jdbc-drivers-external 
  • This location is for the adapters that do not have the drivers included by default.
  • <DENODO_HOME>\lib\extensions\jdbc-drivers-other 
  • This location is for any other JDBC drivers that could be used for example with the Generic adapter.

Denodo 7.0

  • Check whether the driver is located in the following folder.
  • <DENODO_HOME>\lib\extensions\jdbc-drivers
  • This location is for the adapters that have the drivers already included in the product distribution and they should usually not be changed manually.
  • <DENODO_HOME>\lib-external\jdbc-drivers 
  • This location is for the adapters that don't have the drivers included by default.

If you cannot find the driver in the corresponding place, then copy the driver into the corresponding folder for the datasource and version.

Previous to Denodo 7.0

In previous versions of the Denodo Platform it is recommended to create a similar folder structure for each specific data source and version and add the drivers into those folders. You need to reference the folder location that includes the driver jar(s) in the Driver Classpath field of the JDBC data source configuration window.

Oracle JDBC Sources with TNSNAMES like URIs

Once you have made sure that the driver exists in the correct location but the error still persists, check if the format of the database URI is correct.  A common error when importing Oracle JDBC data sources is to use an invalid TNSNAMES like URI.

The URI should be in the following format: jdbc:oracle:thin:@<connection string>

For instance, for a TNSNAMES like URI it should look like this:

jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = <port>))(CONNECT_DATA =(SERVER = <server>)(SERVICE_NAME = <sid>)))

References

Virtual DataPort Administration Guide: Supported JDBC Data Sources

Virtual DataPort Administration Guide: Uploading a JDBC Driver

Local Naming Parameters (tnsnames.ora)

Questions

Ask a question
You must sign in to ask a question. If you do not have an account, you can register here

Featured content

DENODO TRAINING

Ready for more? Great! We offer a comprehensive set of training courses, taught by our technical instructors in small, private groups for getting a full, in-depth guided training in the usage of the Denodo Platform. Check out our training courses.

Training