Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

Re: Issues with Vertica Scheduled refresh

I've already set it up in the ODBC System DSN and in my gateway connections. Yet, when I try to sign in in the database through the dataset options in the web it says the same thing: I don...
  • lbendlin's avatar
    lbendlin
    6 years ago

    No, it's much worse. When you select the "native" Vertica connector in the gateway what you get behind the scenes is the Simba 8.0 ODBC driver that doesn't work for you.

     

    What you _should_ do instead is to use ODBC as the connector, and install the official Vertica 9.01 ODBC driver (from Vertica, not from Microsoft or Simba).

     

    To get rid of the Simba driver issue you probably have to uninstall and reinstall the gateway, or even mess around in the registry.

Anonymous's avatar
Anonymous
Not applicable
6 years ago

Hey lbendlin ! Thank you for replying,

I am using the native vertica connector in the desktop application and in my gateway.



Any suggestions?

lbendlin's avatar
lbendlin
Icon for Super User rankSuper User
6 years ago

That's different from what you state in the original post. Have you switched the connection type around?  Note that it needs to be absolutely consistent between desktop and gateway. The connection strings have to be EXACTLY the same.

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Nope, originally I used those settings but since the error indicated something wrong with the ODBC connector, I set it up anyways (Just to be sure). I already removed the connection in the ODBC and it still throws the same error.
    Yes! I'm aware that the connection string needs to be the same in the gateway and the desktop application. I dont know what might be causing this. Do you have any other ideas of why this might be happening?

    Thank you!

    • lbendlin's avatar
      lbendlin
      Icon for Super User rankSuper User
      6 years ago

      since we have multiple working Vertica gateway connections in our tenant (both ODBC and native) I know that it can be done. We don't use the Simba ODBC driver, we use the one provided by Vertica directly, in version 9.1 I think. Not sure if that makes a difference.

       

      Ony recommendation would be to start over, with a separate dataset and a small table as data source, to see if you can get that to work.

      • lbendlin's avatar
        lbendlin
        Icon for Super User rankSuper User
        6 years ago

        I have to apologize. I just learned that "Simba ODBC"  is the engine behind a lot of the "Extension" type gateway connectors. I was not aware of that. To add insult to injury, that Simba engine is hidden from the regular ODBC settings AND also does not support custom queries (despite being ODBC).

         

        So I have to modify my recommendation to say that you should try to install the genuine Vertica ODBC driver (9.01) and configure it via the genuine ODBC control panel. You need to do this separately on each gateway cluster member.