Archiving Process - Teradata Tools and Utilities

Teradata® Archive/Recovery Utility Reference

Product
Teradata Tools and Utilities
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-06-05
dita:mapPath
fac1527114221922.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
Product Category
Teradata Tools and Utilities

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.