What the Teradata Database Does
When an application is running and the Teradata Database crashes:
Teradata Database sessions and session ids are preserved, and can continue to be used.
All outstanding Teradata Database transactions are aborted and all of the databases
involved are rolled back to the state they would have been in if the transactions
had not begun.
All requests that have not completed are aborted and any work they have performed
is rolled back.
All spool files, including those the Teradata Database has kept for completed requests,
are discarded.
Applications already waiting for a response before the crash/recovery occurs will
be notified (see “What MTDP Does” on page 378).
Applications submitting a request during the crash and recovery process may be notified,
see “What MTDP Does” on page 378.
Applications later using the abort, fetch, rewind, or end request function for a Teradata
SQL request aborted by the crash/recovery process, or submitting a new request in
a transaction that was in progress when the crash occurred and thus was aborted in
the recovery process, will be notified, see “What MTDP Does” on page 378.
If a restart occurs during a logoff request, CLI automatically resubmits the request.