Forum Discussion
Re: Issues with Vertica Scheduled refresh
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.
Super UserIt's complaining about Simba because you chose to use ODBC as the connection type. You need to change your connection type on the desktop and the gateway to the native Vertica driver (unless you have a really good reason for needing ODBC, like custom query etc)
An ODBC (DSN flavor) connection string looks like this:
{"connectionString":"DSN=DATA_DSN"}
A Vertica connection string looks like this:
{"extensionDataSourceKind":"Vertica","extensionDataSourcePath":"server.domain.net;database"}
Hey lbendlin ! Thank you for replying,
I am using the native vertica connector in the desktop application and in my gateway.
Any suggestions?- lbendlin
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.
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!