Transaction Recovery Sequence - Advanced SQL Engine - Teradata Database

Database Utilities

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2020-06-15
dita:mapPath
boh1556732696163.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1102
lifecycle
previous
Product Category
Teradata Vantageā„¢

The general sequence of a Teradata Database system recovery is as follows:

  1. The status of each transaction on each online AMP is determined by the Teradata Database system.

    All of the online AMPs at the time of the restart work together to determine which transactions were complete, and which ones were not completed. Completed transactions are ignored and incomplete ones are backed out. The process of rolling back incomplete transactions might take some time.

    Write and exclusive locks are set against all data modified by incomplete transaction.

  2. All locks needed for the recovery are set, and the Teradata Database system begins roll back or completion of the transactions.
  3. The Teradata Database system accepts work and is operational.
    If new transactions reference the inconsistent data of to-be-rolled-back transactions, they are blocked until the recovery process restores the data and releases the lock.
  4. Down AMP recovery begins.