If Hyper-Q reports the error message
DTM9034: Unsupported reconnect request, it indicates that the Teradata client application lost connectivity with Hyper-Q and is trying to reconnect to the session it was previously connected to.
Hyper-Q responds with the error code indicating to the client that the session it seeks to reconnect to is invalid. For security reasons, each client session is associated with a dedicated session to the backend database and authentication is performed directly against that database. Upon loss of connectivity to the client, Hyper-Q removes the corresponding session to the backend database (and vice versa).
To retry the transaction, open a new connection from the client and resubmit the transaction that was interrupted by the connectivity loss.
In the event of frequent connectivity loss between the client application and Hyper-Q, check the firewalls and routers between the client application and Hyper-Q for settings that drop idle TCP connections, or filter out TCP keepalive messages. A keepalive is a message sent by one device to another to check that the link between the two is operating, or to prevent the link from being broken.