DENODO DRIVER LOADING NEVER ENDS

My configuration is: KNIME Analytics Platform ver 4.6.2 (embedded java ver. 17.0.3.20220429) on UNIX platform
In order to create a connection with DENODO, I download the ODBC driver from <DENODO_HOME>/tools/client-drivers/jdbc (file: denodo-vdp-jdbcdriver-7.0-update-20200310)
My goal is to connect a DENODO DB by completing the following procedure:
1)In the KNIME application, navigate to File > Preferences > KNIME >Database Driver
2)Load the JDBC driver corresponding to Virtual DataPort server that can be retrieved from the directory <DENODO_HOME>/tools/client-drivers/jdbc.
3)After registering the driver, use ‘Database Connector’ to access the Virtual DataPort server elements since it is used to create a connection to the arbitrary JDBC databases for which the driver is not available within the KNIME Platform.
4)Configure the Database Connector with the Database driver as ‘com.denodo.vdp.jdbc.Driver’ and provide the Database URL as follows,
jdbc:vdb://:/[?=[&=]* ]
where the parameters provided within the square bracket are optional and provide the hostname, port and databaseName corresponding to your Virtual DataPort server that you are connecting to.
5)And provide the necessary credentials for authentication purpose.
6)Once the configuration is done, you could test the connection by executing the newly created Database Connector.

My problem is that the Step 2 never ends. I mean the loading step of the ODBC driver is still in progress and never ends. We tried several times to “stop and restart” but the result is always the same.

If the issue would be caused by an incompatibile versions between embedded JAVA version on KNIME and the DENODO driver, I expect an error on the connection test and not a never ending step.

Some of you have already experienced this issue? how did you solve it?
Thanks in advance for your support

Hi @bperPCA and welcome to the forum.

According to their documentation (Access Through JDBC — Virtual DataPort Developer Guide) the JDBC drivers for Denodo require Java 8/9/10/11. Since the latest version of KNIME runs Java 17, I wonder if that might be an issue? It’s possible that a previous version of KNIME AP 4.5 might not exhibit this behavior, since it’s based on Java 11.