16.10 - Down AMPs - Parallel Transporter

Teradata Parallel Transporter Reference

Product
Parallel Transporter
Release Number
16.10
Published
July 2017
Content Type
Programming Reference
Publication ID
B035-2436-077K
Language
English (United States)

The impact of down AMPs on the Update operator depends on the following:

  • The number of AMPs that are down, either logically or physically, in a cluster
  • The operational phase of the Update tasks when the down AMP condition occurs
  • Whether the target tables are fallback or nonfallback

The following table describes the impact of down AMPs on Update operator tasks on fallback and nonfallback tables.

AMP Usage 
Condition 1 Condition 2 Result
All of the target tables are fallback Not more than one AMP is down Update operator tasks continues to run as long as there is not more than one AMP down, either logically or physically, in a cluster.

The down AMP does not participate in the application phase if:

  • The AMP goes down before the Update operator tasks enter the application phase, and the AmpCheck attribute is set to 'None'
  • Certain I/O errors occur during the application phase
Two or more AMPs are down Update operator tasks do not run, or terminate if two or more AMPs are down, either logically or physically, in a cluster.
In the application phase, if AMPs are down to the extent that data on the DSU is corrupted, then you must restore the affected tables.
One or more of the target tables is nonfallback One or more AMPs are down Update operator tasks terminate and you cannot restart until all of the AMPs are back up.
The Update operator also terminates if I/O errors corrupt the target tables in the application phase.