Exasol Database Connection Not Working!

[Lord-Vader]

Hello fellow Talenders, I am trying to make a connection with Exasol database SaaS, but it doesn't work.

I contacted Exasol and they too can reproduce the issue. They found another solution via JDBC connection, but it is not optimal. First I kept getting a connection error and than I began getting an authentication error(see images). I can connect via the JDBC Connection(see images), but I can't do certain things, like I can do with the DBconnection components.

I think the issue may sit in the config of the DB Type self. I don't fully understand on how to change things, so I don't know how to change it for testing.

Talend Version: Talend Open Studio Data integration(8.0.1.2021119_1610)

Java version:

jdk-16.0.02 , jdk 17 or 19 doesn't make a difference.

Exasol JDBC: 7.1.14

Any help will be appreciated.

[Anonymous]

You appear to have two outcomes in your failure screenshots. A refusal and a timeout. I couldn't see the different between these two situations. Was there a difference? Also, can you create a connection with the tDBConnection component?

I am afraid I do not have an Exasol DB to try this out myself.

[jlolling]

I know this issue. In the JDBC connection you use a finger print inside the url I guess (thats what you have covered). This works with the newest driver from Exasol but unfortunately Talend ships with an older driver, which does not have this feature.

I suggest to simply remove the fingerprint and it should work.

[jlolling]

I also recommend not to use the driver file shipped or downloaded from the Exasol web side because here you do not have any version information in the file name. Better you get the file from Maven Central: https://search.maven.org/artifact/com.exasol/exasol-jdbc

Now you know exactly the version and the file is correctly named. Later on you can use a more recent driver and can distinguish between both.

Exasol is keeping the repository updated as well as their own download.

[Lord-Vader]

No I cannot make a connection via tDBconnection(exasol). Sorry I didn't explain my situation perfectly. When I tried to make a connection at first I was inserting the wrong information that was provided, as in I was putting my IP in like the docs said instead of the connection string that was given of the cluster. But then I began having this authentication error meanwhile I can successfully see my database via DBeaver, DBvisualizer, PowerBI for example. I never made a connection via de tDBconnection(exasol), only via jdbc.

tDBconnection with the exasol database does not work. I gave another example with the job for reference to see what I mean.

exasol docs : https://docs.exasol.com/saas/connect_exasol/data_integration_etl/talend.htm

[Lord-Vader]

I am not using the fingerprint, I am using just the connection string of the cluster. example: "o2grer4b3gf8bfdwuhqbdsucbgouyrg.clusters.exasol.com"

[Lord-Vader]

Ok I have changed it to the version you recommended.

[Anonymous]

Did this resolve your issue?

[Lord-Vader]

This was not an issue. I don't have an issue when connecting via the "DB Type - JDBC". The issue is that with "exasol tDBconnection" or the "DB Type - Exasol" it doesn't connect, it keeps giving me the authentication error. I also tried retrieving schema but it throws the same auth error.

 

If I point out the jar file path via the install new module via the "DB Type JDBC" it does work, but I don't want that. I want to use the tDBConnection Exasol. I tried erasing the old jdbc 6.0.9302 folder and restarting Talend with a new folder named exactly the same but with the new driver and new numbers etc(see image). but still it did not work. It keeps making me install the old 6.0.9302 version. It does not recognize the newer version when I put it in the folder like in the image.

But when I do retrieve schema with the "DB Type JDBC" it asks me for the 7.1.16 snapshot jar file(see image).

Folder path to jars: C:\Program Files (x86)\TOS_DI-8.0.1\studio\configuration\.m2\repository\org\talend\libraries

Hopefully this is enough info to cover what I am trying to explain. But if you need more info just let me know.

 

[Anonymous]

I have just signed up to the Exasol free trial to test this out and see if I can recreate this issue. Unfortunately (or fortunately) I cannot recreate this. It just works. I am using TOS v8. How might your config be different to the free trial in terms of connection configuration?