Why Vertica ODBC driver v 12 refer to non-existing dir for reporting error message
I got error message from app that uses Vertica ODBC driver v 12:
[Vertica][DSI] An error occurred while attempting to retrieve the error message for key 'VPrepareError' with message parameters ['no connection to the server
'] and component ID 101: Could not open error message files - Check that "/opt/vertica/lib64/en-US/VerticaMessages.xml" or "/opt/vertica/lib64/VerticaMessages_en-US.xml" exists and are accessible.
Xml files do exist, bu many-many versions ago they were moved to /opt/vertica/us-en.
Apparently, hardcoded dir name for XML messages have not been changed .
Install is standard vertica-client rmp:
$ rpm -qa|grep vertica-client
I do not have any reference to Vertica driver in /etc/odbc.ini, or /etc/odbcinst.ini.
I am using driver connect string, where you are specifying driver file name with full path.
in isql, that would be options -3 and -k.
This error - incorrect XML dir - do exist for many years, but I thought it was fixed in recent driver version. To my big surprise, error still there.