You can translate the question and the replies:

Cannot connect to JDBC database for Lab

I'm going through the Lab: DEN60EDU0105LAB01 - Create ds_call_center data source and import all tables I've installed * Denodo * AccessDatabaseEngine_X64 Calltracking.mdb is in: C:\Users\ehayes\Desktop\Denodo\DEN60EDU0105LAB01 I've configured the C:\Windows\System32\odbcad32.exe to look at database above I set all the parameters of the new JDBC connection I'm getting error: Unable to establish connection: sun.jdbc.odbc.JdbcOdbcDriver I did restart denodo, and my DSN is now showing in the list, but still getting same error when I try to connect to it. Log: 238975 [SwingWorker-pool-1-thread-5] ERROR 2018-08-28T15:41:30.908 com.denodo.vdb.admin.model.vdbserverproxy.VDBServerProxy - sun.jdbc.odbc.JdbcOdbcDriver com.denodo.vdb.vdbinterface.common.clientResult.VQLException: sun.jdbc.odbc.JdbcOdbcDriver at com.denodo.vdb.vdbinterface.client.printer.GetVDBObjectPrinter.format(Unknown Source) at com.denodo.vdb.vdbinterface.common.clientResult.ErrorResult.accept(Unknown Source) at com.denodo.vdb.vdbinterface.client.VDBProxy.exec(Unknown Source) at com.denodo.vdb.vdbinterface.client.VDBProxy.exec(Unknown Source) at com.denodo.vdb.admin.model.vdbserverproxy.VDBServerProxy$4.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at com.denodo.vdb.admin.model.vdbserverproxy.VDBServerProxy.execute(Unknown Source) at com.denodo.vdb.admin.model.vdbserverproxy.VDBServerProxy.execStatement(Unknown Source) at com.denodo.vdb.admin.model.wrapper.WrapperAdminFacade.testJDBCConnection(Unknown Source) at com.denodo.vdb.admin.model.introspect.VQLSourceIntrospectionService.testJDBCConnection(Unknown Source) at com.denodo.vdb.util.introspectionservice.util.jdbc.JDBCAdminUtil.testConnection(Unknown Source) at com.denodo.vdb.util.introspectionservice.util.odbc.ODBCAdminUtil.testConnection(Unknown Source) at com.denodo.vdb.admin.gui.components.dockable.datasources.edition.CreateODBCDataSourceDialog$9.doInBackground(Unknown Source) at com.denodo.vdb.admin.gui.components.dockable.datasources.edition.CreateODBCDataSourceDialog$9.doInBackground(Unknown Source) at javax.swing.SwingWorker$1.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at javax.swing.SwingWorker.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
JDBC Access
user
28-08-2018 15:15:53 -0400
code

3 Answers

Hi, I followed the instructions provided in 'DEN60EDU0105LAB01 - Create ds_call_center data source and import all tables' and was able to successfully connect to the ODBC datasource. I did the following steps: * Downloaded and installed AccessDatabaseEngine_X64 * In ODBC Data Source Administrator (64-bit) Windows tool, ‘Add..’ a new System DSN. * Select Microsoft Access Driver in ‘Create New Data Source’ * In the ODBC Microsoft Access Setup window, Select ‘calltracking.mdb’ as Database and give the DSN a name ‘call_tracking’ * In Virtual DataPort Administration Tool, create a new ODBC Data Source with the following details: * Name: ds_call_center * Change the Database Adapter: ‘Access’ * Connection type: DSN * DSN: ‘call_tracking: System DSN’ * Enter the login and password For this scenario, I would ensure that the Microsoft Office which I have is a 64-bit version as well. If you are running the Virtual DataPort Server on Linux, you will have to enable the support for ODBC data sources as it is disabled by default. You may refer to [Enabling the Support for ODBC Sources When the Virtual DataPort Server Runs on Linux](https://community.denodo.com/docs/html/browse/7.0/platform/installation/postinstallation_tasks/postinstallation_tasks_in_virtual_dataport/enabling_the_support_for_odbc_sources_when_the_virtual_dataport_server_runs_on_linux) section of the Denodo Platform Installation Guide for more information. Hope this helps!
Denodo Team
29-08-2018 05:19:42 -0400
code
I followed all those instrauctions, and still no luck. I dont automatically see the system DSN that I configured. But I do see the User DSN. The User DSN shows up as "callcenter6 : User DSN" without quotes. I tried removing the space after the DSN Name and the colon. I also tried using the syntax your example uses for the System DSN I set up. Still no luck. For what it's worth, I was able to get the data source (callcenter6) working in Exel. So From what I can tell, the data source is configured properly As the path in my originaly post would indicate, I'm using Windows.
user
29-08-2018 10:29:59 -0400
From Denodo Support: The JDBC-ODBC bridge has been removed from the standard Oracle JRE 8 (https://docs.oracle.com/javase/7/docs/technotes/guides/jdbc/bridge.html). For that reason, you are getting the error when creating the ODBC data source.Try using the internal JVM shipped with Denodo Platform (it included all the necessary libraries).
user
06-09-2018 12:55:21 -0400
You must sign in to add an answer. If you do not have an account, you can register here