Copying a Table to a Different Configuration - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

An archived data table named Personnel.Department is copied to a different Teradata Database in this example:

COPY DATA TABLE (Personnel.Department)
   ,FILE = ARCHIVE;

The table has the same name in the target database that it had in the archived database, and belongs to a database named Personnel on the target Teradata Database. In the example, if:

  • A database named Personnel does not exist on the target database, Teradata ARC rejects the copy operation.
  • A table named Personnel.Department does not exist in the target database, Teradata ARC creates one.
  • The data table being restored has permanent journaling on the source system, it has permanent journaling on the target system as well.
  • Teradata ARC creates a new table for the copy operation, the target journal table is the default journal for database Personnel. Otherwise, the target journal table is the journal table associated with the table that is being replaced on the target system.
  • Teradata ARC creates a new table for the copy operation and the Personnel database does not have a default journal, then Teradata ARC rejects the copy operation.