Consider setting the configuration parameter 'TLSRenegotiationLimit' to zero

TLSRenegotationLimit is a db configuration parameter not an ODBC DNS setting. It does control the amount of data returned by the server before a TLS Renegotiation is triggered.

Unfortunately for you , it was only introduced in version 9.2.1 (the default being zero). Prior to 9,2,1 that parameter could not be controlled and the default could result in the issue you are seeing when reading larger amount of data.

The version of the ODBC Driver you are using is leveraging the schannel which doesn't handle TLS renegotiation, hence the error you're seeing.

9.0.1 is pretty old, you might want to consider upgrading ?

If you can't upgrade Vertica nor downgrade the ODBC driver, the only workaround might be to insure your queries don't return "too much" data.

TLSRenegotationLimit is a db configuration parameter not an ODBC DNS setting. It does control the amount of data returned by the server before a TLS Renegotiation is triggered.

Unfortunately for you , it was only introduced in version 9.2.1 (the default being zero). Prior to 9,2,1 that parameter could not be controlled and the default could result in the issue you are seeing when reading larger amount of data.

The version of the ODBC Driver you are using is leveraging the schannel which doesn't handle TLS renegotiation, hence the error you're seeing.

9.0.1 is pretty old, you might want to consider upgrading ?

If you can't upgrade Vertica nor downgrade the ODBC driver, the only workaround might be to insure your queries don't return "too much" data.

HI SergeB,

Thank you for confirming my biggest doubts! But atleast now I know its not Power BI (on which all fault [is still] being pinned). Since Vertica DB is production one and I dont have an control or authorization to upgrade it, I will go with the Driver upgrade route.

Luckily I was able to install ODBC driver 9.0.x on all Power BI Gateway cluster and so far haven't seen this issue resurface.

I hope keeping this version of ODBC driver would mean that I would not see this issue again.. right??

Thank you so much again for helping me out!!

Hi @SamRock , did you also have the same issue when loading data into power bi desktop?
Error:
OLE DB or ODBC error: [DataSource.Error] ERROR [HY000] [Vertica][VerticaDSII] (20)
An error occurred during query execution: Renegotiate requested by the server.
Schannel does not support renegotiation. For vertica server versions above 9.2.1,
consider setting the configuration parameter 'TLSRenegotiationLimit' to zero.
The connection will be closed. server closed the connection unexpectedly
This probably means the server terminated abnormally before or while processing the request. .

I tried installing the driver 9.0.x in my computer but i keep getting the same error when loading more than 2.5M Rows

@Juaneve3529 said:
Hi @SamRock , did you also have the same issue when loading data into power bi desktop?
Error:
OLE DB or ODBC error: [DataSource.Error] ERROR [HY000] [Vertica][VerticaDSII] (20)
An error occurred during query execution: Renegotiate requested by the server.
Schannel does not support renegotiation. For vertica server versions above 9.2.1,
consider setting the configuration parameter 'TLSRenegotiationLimit' to zero.
The connection will be closed. server closed the connection unexpectedly
This probably means the server terminated abnormally before or while processing the request. .

I tried installing the driver 9.0.x in my computer but i keep getting the same error when loading more than 2.5M Rows

Make sure you are creating an ODBC DSN and not use the native Vertica connector in Power BI