ODBC Driver Error: "The Connect Series for ODBC Greenplum Wire Protocol driver is only licensed to connect to Greenplum databases."

Products

• VMware Tanzu Greenplum

Issue/Introduction

Using ODBC connection to a greenplum, at some stage the connection stops working and the ODBC DataDirect driver generates the following error message:

'You are attempting to connect to the following type of server'

SQLSTATE = S1000
NATIVE ERROR = 1208
MSG = [DataDirect][ODBC Greenplum Wire Protocol driver]The Connect Series for ODBC Greenplum Wire Protocol driver is only licensed to connect to Greenplum databases.  You are attempting to connect to the following type of server:

SQLSTATE = S1000
NATIVE ERROR = 1208
MSG = [DataDirect][ODBC Greenplum Wire Protocol driver]The Connect Series for ODBC Greenplum Wire Protocol driver is only licensed to connect to Greenplum databases.  You are attempting to connect to the following type of server:

SQLSTATE = S1000
NATIVE ERROR = 1208
MSG = [DataDirect][ODBC Greenplum Wire Protocol driver]The Connect Series for ODBC Greenplum Wire Protocol driver is only licensed to connect to Greenplum databases.  You are attempting to connect to the following type of server:

(Please note the empty string at the end of the error)

Environment

Product Version: 4.3

Resolution

You can confirm any error message by configuring the odbc configuration/test section: 
 https://docs.vmware.com/en/VMware-Greenplum/5/greenplum-database/datadirect-datadirect_ODBC_71.html 

An application lost access to greenplum around the same time the vacuum warning started to show up in master log:

2019-10-26 17:57:24.666451 WIB,"gpmon","gpperfmon",p1656,th-1677113568,"127.0.0.1","29617",2019-10-26 17:57:24 WIB,0,con27675,cmd1,seg-1,,,,sx1,"WARNING","01000","database ""postgres"" must be vacuumed within 1299734607 transactions",,"To avoid a database shutdown, execute a full-database VACUUM in ""postgres""."

According to this Progress Knowledge Base, the ODBC DataDirect driver doesn't handle a vacuum warning: 
https://knowledgebase.progress.com/articles/Article/Greenplum-ODBC-driver-does-not-handle-vacumm-db-warning 

This issue is fixed is in hot fix 07.01.0101 (B0152, U0096) and 07.16.0256 (B0314, U0208).

Solution: Upgrade ODBC driver to the latest version on the Pivotal Network