Application Behavior When SET CRASH = WAIT_NOTELL - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905
The behavior of embedded SQL applications when a node resets, SET CRASH = WAIT_NOTELL, and the application is running on any of the following environments is explained following the list:
  • Non-resetting node
  • Workstation-attached client
  • Mainframe-attached client

The application reconnects its session and returns one of the following error codes from the database; the embedded SQL application takes action appropriate to the error condition:

Code Description
Error 2825 No record of the last request found after Teradata Database restart.
Error 2826 Request completed but all output was lost due to Teradata Database restart.
Error 2828 Request was rolled back during Teradata Database recovery.
Error 3120 Request aborted because of a Teradata Database recovery.