During an archive of a Teradata Database, Teradata ARC issues messages in the format shown below as it archives different types of objects. The format of the byte and row counts agree with the format of these counts in the restore or copy output.
FUNCTION "UDFname" - n,nnn,nnn BYTES, n,nnn,nnn ROWS ARCHIVED JOURNAL "Journalname" - n,nnn,nnn BYTES ARCHIVED MACRO "macroname" - ARCHIVED METHOD "methodname" - ARCHIVED METHOD "methodname" - n,nnn,nnn BYTES, n,nnn,nnn ROWS ARCHIVED PROCEDURE "procedurename" - n,nnn,nnn BYTES, n,nnn,nnn ROWS ARCHIVED TABLE "tablename" - n,nnn,nnn BYTES, n,nnn,nnn ROWS ARCHIVED TRIGGER "triggername" - ARCHIVED TYPE "UDTname" - ARCHIVED VIEW "viewname" - ARCHIVED
When the objects are archived, Teradata ARC issues this message:
DUMP COMPLETED
At the start of each database archive operation or after a system restart, the output listing shows all offline AMPs.
If an archive file contains a selected partition archive of a table, a message reports the bounding condition that was used to select the archived partitions and whether the bounding condition is well-defined.
If online logging is initiated for one or more tables during an archive, online logging information is displayed for each of the tables in the output listing.