Exasol ODBC Driver Failing to Retry Alternative Hosts with Kerberos Authentication When Reserve Node is Unavailable
Details
| Detail name | Value |
|---|---|
| Changelog Number | 28497 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.1.0 |
| Fix Versions | ODBC 26.2.7 |
| Resolution Date | 2026-06-30 |
Description
When using the Exasol ODBC Driver with Kerberos Authentication, the driver randomly selects a host from the provided list, including reserve nodes. If the selected host is a reserve node and the database is unavailable on that node, the driver is expected to retry other hosts from the list. However, when Kerberos Authentication is enabled, the driver does not attempt to connect to other nodes when the initially-selected node fails. This results in connection failures and the following exception message:
[Exasol][Exasol Driver]Connection lost. Please make sure that the server supports Kerberos authentication.
Workaround
As a temporary measure, users were required to manually remove reserve nodes from the list of hosts when connecting via the Exasol ODBC Driver with Kerberos Authentication.
Fix
Issue was fixed.
