16.10 - Transaction Recovery Sequence - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
zll1480972831047.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval

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.