08-29-2017 04:22 AM - edited 08-29-2017 04:42 AM
I am trying to establish a connection between SAS & AWS Athena. I am working on RHEL 6.7, java version is 1.8.0_71.
I have SAS/ACCESS to ODBC installed.
Could someone advise how to configure that please?
So far, after some reading on "Accessing Amazon Athena with JDBC" , I have tried a 'maybe it will work' naive approach with trying to set a DSN in odbc.ini files (outside of SAS): I have downloaded Athena JDBC jar file and tried configuring connection in a similar way I did it for EMR.
As expected, it didn't work and iODBC throws the following:
iODBC Demonstration program This program shows an interactive SQL processor Driver Manager: 03.52.0709.0909 Enter ODBC connect string (? shows list): DSN=ATHENA 1: SQLDriverConnect = [iODBC][Driver Manager]/opt/amazon/hiveodbc/lib/64/AthenaJDBC41-1.1.0.jar: invalid ELF header (0) SQLSTATE=00000 2: SQLDriverConnect = [iODBC][Driver Manager]Specified driver could not be loaded (0) SQLSTATE=IM003
As someone commented on SO, I should try using some ODBC-JDBC bridge but not sure how to approach this topic - all I have found so far covers accessing ODBC source, but that is not the case here (there is only jdbc driver for Athena).
Has anyone tried making such connection before? Is it even possible?
08-29-2017 04:15 PM - edited 08-29-2017 04:15 PM
There are ODBC to JDBC bridges. DataDirect provides one called SequeLink. You can find out about it here: https://www.progress.com/connectors/sequelink
PROC GROOVY can do this...
LilyAnne Zhang wrote an excellent SAS Global Forum paper on this topic.
Accessing DBMS with the Groovy Procedure and a JDBC Connection.
Hope this helps,
09-22-2017 10:18 AM
I have installed ODBC-JDBC bridge from Easysoft, configured connection and tested using isql with -v -e options.
However, in SAS I am getting CLI prepare error:
Is there any way to cope with that in SAS?
Tried using dbidirectexec option (wanted to force SQLExecDirect instead of SQLPrepare & SQL Execute ) but no luck with that too.
I have opened a Support Track with SAS but no luck so far - hoping that someone may have experienced something similar in the past