Forum Discussion

merinmione's avatar
merinmione
Helper I
6 years ago

Prepared statements? Amazon Redshift ODBC Error prepared statements

hi, i'm trying to connect to an Amazon redshift database to get Greenhouse data (recruiting system) but i keep getting an error.

 

DataSource.Error: ODBC: ERROR [42P05] [Microsoft][Amazon Redshift] (30) Error occurred while trying to execute a query: [SQLState 42P05] ERROR: prepared statement "PGODBCStmt-ExternalSchema" already exists

 

My system vendor explains that "the prepared statement error likely indicates your tool is attempting to use prepared statements to query Redshift. Our firewall does not allow prepared statements, so you'll need to tell your tool to not use them. "

How do i do that? Ideas? 

Need Help

28 Replies

      • mwegener's avatar
        mwegener
        Most Valuable Professional
        6 years ago

        Unfortunately I have no experience with Amazon Redshift.

        I always thought prepared statements would be the preferred (secure) query type.

         

         

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Hi merinmione 

     

    Did you get any resolution to this?

     

    I am having the exact same problem trying to access Greenhouse data via Redshift in Power BI and am really struggling to troubleshoot. We have tried the built-in Redshift driver in Power BI plus also other ODBC drivers but still experiencing errors. And I got the same feedback from Greenhouse and no other help from them.

     

    I'd be grateful for any feedback or learnings you have!

    • merinmione's avatar
      merinmione
      Helper I
      6 years ago

      I submitted a ticket with PowerBi and they are working through their vendor that does the actual redshift connections. It's been two weeks.  I'll post when i learn anything of value. Not yet. But I do get updates.

    • merinmione's avatar
      merinmione
      Helper I
      6 years ago

      Anonymous I'm still having my issue and no help from Greenhouse either. Have you got any other update?

      • Anonymous's avatar
        Anonymous
        Not applicable
        6 years ago

        I've collected a support ticket and I've been collecting records for them. They're still investigating, but so far they think it's a problem with the Power BI Redshift driver, so they've scaled it to Simba. I'll update you if I get any progress

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Following this thread as we got the same error using Tableau with Amazon Redshift connector to Greenhouse. Been using it for 6 months with no issues, then all of a sudden our Tableau online extract refreshes started failing with the exact same error message.

     

    It only seems to be impacting our tableau online extract refreshes, we are able to connect using Tableau desktop and refresh fine aswell as connect tableau online workbooks to amazon redshift. 

     

    Hopefull if you are able to resolve with PowerBi it could be the same issue in Tableau. 

    • merinmione's avatar
      merinmione
      Helper I
      6 years ago

      wasn't able to resolve with power bi. had to get a new ODBC connection method from GH. i haven't tested it yet though.

      • Anonymous's avatar
        Anonymous
        Not applicable
        6 years ago

        thank you, if you wouldn't mind confirming when you have tested we may go the same route and ask GH for new connection details. 

    • merinmione's avatar
      merinmione
      Helper I
      6 years ago

      I've tested the PostgresSQL's ODBC that GH gave me and it worked. I had one table that gave me an error, that the fetched item was truncated. But i don't need that table, so I didn't select it next time and it worked fine.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Any luck resolving this issue?  I'm running into the exact same problem.

    • th340385's avatar
      th340385
      Helper I
      5 years ago

      I am having the same issue as well. Did you happen to resolve yet? We have reached out to GH and they are pointing the issue back to Microsoft. 

      • Anonymous's avatar
        Anonymous
        Not applicable
        5 years ago

        No, I didn't have any luck.  GH referred me to their PostGreSQL alternative.  Which works, but is slower and will result in truncation errors for certain tables.