Possible Data-Loss Condition
In some cases, data might be lost if sessions are aborted by:
After a Teradata Database restart, BTEQ sends a request or fetch on the active session, then CLI starts the reconnect procedure. If a session is idle, it does not send a request or fetch, and CLI cannot perform the reconnect.
Note: The 20-minute period is the default value of a gateway configuration specification. The period might be different for local systems.
In these cases, the Teradata Database returns error code 8018 (Session id is illegal) or 8055 (The session has been forced off) to BTEQ. This means that the Teradata SQL response has been discarded, and the request and the transaction in which it was embedded have been aborted and backed out.
The severity of this condition depends on the nature of the transactions that were running when the session was aborted:
In either case, the aborted request must be manually resubmitted.