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

At first it said that it needed to set the TLS Authentication to 0 but I managed to fix that. Now It just gets stuck and some time after it doesn't load any more rows, it throws this error:

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

That's actually an issue in your source data.  That's very much an invalid timestamp!

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    You're right! Thank you for your help 🙂