Archiving Process - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
15.00
Language
English (United States)
Last Update
2018-09-25
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

Archiving Process

Database SYSUDTLIB is linked with database DBC and is only archived if DBC is archived. SYSUDTLIB cannot be specified as an individual object in an ARCHIVE statement.

If database DBC is involved in an archive operation, it is always archived first, followed by database SYSUDTLIB. Any additional databases that are being archived follow SYSUDTLIB in alphabetical order.

By default, Teradata ARC counts output sectors and output rows. The row count is the number of primary data rows archived when the DATA or NO FALLBACK option is specified. Both counts are included in the output listing.

Archives have these limitations:

  • When using the multi-stream feature, a dictionary only archive must be run as a single-stream job.
  • Journal and data (or dictionary) tables cannot be stored on the same archive file.
  • When a journal table is archived, the saved subtable portion of the journal is archived. If two archives are performed without doing a CHECKPOINT WITH SAVE operation in between, the two archive files are identical.
  • If an archive is created when the saved subtable is empty, the archive file contains only control information used by Teradata ARC.
  • Archive Messages

    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.

    Archive Results

    After each archive operation, review the listing to determine whether any non-fallback tables were archived while AMPs were offline. If any AMPs were offline during the archive, create a specific AMPs archive for those tables. When the offline AMPs are brought back online, use this archive to complete the operation.

    Teradata ARC does not completely archive data tables that are in the process of being restored or data tables that are involved in a load operation (by FastLoad or MultiLoad). If tables are being restored or loaded, Teradata ARC archives only enough data to allow tables to be restored empty and issues a message.

    Archive Limitation

    Tables with unresolved referential integrity constraints cannot be archived. An unresolved constraint occurs when a CREATE TABLE (child) statement references a table (parent) that does not exist. Use the SQL command CREATE TABLE to create the parent (that is, referenced) table and resolve these constraints. For more information, refer to the Introduction to Teradata.