This example illustrates how a journal table that has some nonfallback images spread across two separate archive files (because an AMP was down at the time of an all-AMPs archive operation) is restored:
COPY JOURNAL TABLE (PersonnelJnlDB.PermanentJournal) (APPLY TO (Personnel.Employee, Personnel.Department)) ,NO BUILD ,FILE = ARCHIVE1; COPY JOURNAL TABLE (PersonnelJnlDB.PermanentJournal) (APPLY TO (Personnel.Employee, Personnel.Department)) ,FILE = ARCHIVE2;
When restoring to a different configuration, Teradata ARC redistributes journal images among all the AMPs. Teradata ARC builds the journal only after it completes the all-AMPs data table archive operation.
To perform this operation:
- Copy the all-AMPs archive and specify the NO BUILD option.
- Copy the specific-AMP archive, but do not specify the NO BUILD option.
This operation is only allowed if the applicable data tables are already copied into the target system. In the example, the archive of all AMPs (except the AMP that was offline) is called ARCHIVE1. The archive of the AMP that was offline at the time of the main archive is called ARCHIVE2.
Teradata ARC copies only checkpoint journal images and images associated with the tables named Personnel.Employee and Personnel.Department to the target system. Teradata ARC discards all other journal images.