Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Amazon Aurora PostgreSQL ODBC - Connection Failure after upgrade to 2022.1.1.40869

ThomasT
8 - Asteroid

Hi all, 

 

after updating Alteryx to 2022.1.1.4 today we suddenly lost our data connection to Amazon Aurora (run via ODBC - Simba PostGreSQL ODBC Driver 1.04.45.1001). 

 

While all table load up just fine, testing the SQL Query comes up with following error "Error SQLPrepare: [Simba]PostgreSQL] (40) Unknown data type: [SQLState HY000] 19 at column %2%"

 

We've tried 5+ tables and it's the same error over and over again. The minute we've downgraded Alteryx back to 2020.3 it all worked just fine again. 

 

Anybody has a clue how to resolve this issue?

 

I found an article that point to using MySQL ODBC for Amazon Aurora, but I was not able to establis a connection through that ODBC connector. 

https://help.alteryx.com/2021.4/DataSources/Aurora.htm

ThomasT_0-1666934996161.png

 

Thanks,

Thomas

4 REPLIES 4
AndrewSu
Alteryx Alumni (Retired)

@ThomasT , this looks like something that needs to be submitted to the support team. 

 

Please submit a case at the link below.

 

https://alteryx-community.force.com/CustomerCasePortal/s/createrecord/New_Case_Portal_Case?lang=en

 

If this helps resolve your issue, please mark this post as a solution so that others in the community can benefit from our collaboration. 

 

Thanks.

apathetichell
19 - Altair

What happens if you cast that specific column as string? What do you have in your Data Type Configuration in your ODBC 64 settings? And you have this set up as Greenplum in your In-DB connections? Usual 2022.1 advice is "turn off amp."

 

@AndrewSu- that Aurora page really needs to be updated - it's only relevant for Aurora MySQL instances - no?

ThomasT
8 - Asteroid

@AndrewSu @apathetichell I've finally worked out the issue. I had to change the ODBC driver from "Simba PostgreSQL" to the "PostgreSQL ANSI (x64)" driver. The MySQL driver listed on the Alteryx page did not work at all. 

 

Even though the DB guys said there was no changes, I assume that soem string formatting took place and it required some form of ANSI decoding to work. 

 

For reference, link to the lastest Postgre drivers that worked for us:

"https://www.postgresql.org/ftp/odbc/versions/msi/"

AndrewSu
Alteryx Alumni (Retired)

Thanks for the update @ThomasT . @apathetichell , I've alerted the documentation team to review.  

 

Please mark this post as the solution so that other's in the community can benefit from our collaboration. 

 

Thanks!

Labels
Top Solution Authors