Archiving Objects - 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
An archive operation copies database information from the Teradata Database to one or two client resident files. The archive can be from any of the following:
  • All AMPs
  • Specified clusters of AMPs
  • Specified AMPs
In general, Teradata ARC archives have these characteristics:
  • If an ARCHIVE statement specifies more than one database, Teradata ARC archives the databases (except for DBC and SYSUDTLIB) in alphabetical order. Within each database, all related objects are archived in alphabetical order.
  • If the statement specifies multiple individual objects, Teradata Archive/Recovery Utility archives the objects in alphabetical order first according to database and then by object.
  • If an archive of database DBC is interrupted for any reason, the entire archive must be performed again. It is not possible to restart an archive operation on database DBC.
  • Archives cannot contain both data tables and journal tables. A journal table archive contains only the saved portion of the table.
  • Journal table archives do not delete change images from the journal table. To accumulate change images for several activity periods, execute a checkpoint with save after each period. Then archive the table without deleting the journal.
  • When performing an archive, do not make any DDL modifications to change the definition of any of the objects being archived.
  • Beginning with TTU 13.00.00, there is support for archiving all objects as individual objects. For a complete list of objects supported by Teradata ARC, see Database Objects.