If a recovery is performed while AMPs are offline and the tables being recovered have fallback, the Teradata Database automatically generates the necessary information to recover the tables when the offline AMPs come back online. However, if the recovery includes tables without fallback, or if the recovery is from a cluster archive, restart recovery when the AMPs come back online.
Be especially careful of performing a rollforward operation on tables without fallback and with a single (local or remote) journal. If this type of operation uses the current journal as input with an offline AMP, the AMP that uses the offline AMP as its backup is not rolled forward. However, if the RELEASE LOCK option is specified on the rollforward operation, HUT locks are released on all AMPs except those that are down and nonfallback tables that have single after images and a down backup.
A similar option, the BACKUP NOT DOWN option, is available for the RELEASE LOCK statement.
Roll forward nonfallback tables with HUT locks remaining (because of a down backup AMP) when the down AMP is brought back online. Also, roll forward the down AMP when bringing it back online.