Driver not found error using tsnames like URL

Applies to: Denodo 7.0 , Denodo 6.0 , Denodo 5.5 , Denodo 5.0
Last modified on: 11 Apr 2018
Tags: JDBC data sources Oracle

Download original document

You can translate the document:

Content

If encountering a “driver not found” error when trying to connect to a data source, first check that the proper driver exists in the folder located at: <DENODO_HOME>/lib-external/jdbc-drivers/database name - version. If it is not there, then copy the driver into the folder.

Starting from Denodo Platform 7.0 the folder <DENODO_HOME>/lib-external/jdbc-drivers/database name - versions  will be already created per each supported data source in order to copy the drivers there.

In Denodo 6.0 and older versions it is recommended to create a similar folder structure for each specific data source and version and add the drivers into those folders. You can reference the folder location in the Driver Classpath field of the JDBC data source configuration window.

If the driver does exist then check the format of the database URI.  A common error when importing Oracle JDBC data sources is to use an invalid TSNAMES like URI.

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

For instance, for a TSNAMES 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

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