Copying a Table to a New Table or Database - 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 is copied under new database and table names to a different Teradata Database in this example:

COPY DATA TABLE (Personnel.Department)
   (FROM (OldPersonnel.Dept)
   ,WITH JOURNAL TABLE = PersonnelJnlDB.PermanentJournal
   ,NO FALLBACK)
   ,FILE = ARCHIVE;

In the example:

  • The new database name is Personnel; the old database name is OldPersonnel. The new data table name is Department; the old data table name is Dept.
  • If a database named Personnel does not exist in the target system, Teradata Archive/Recovery Utility rejects the copy operation.
  • If a data table named Department does not exist in the Personnel database on the target system, Teradata ARC creates one with that name.
  • The WITH JOURNAL option indicates to carry journaling over from the old Teradata Database to the new Teradata Database for this table. In the example, the user copies journal images into the permanent journal table named PersonnelJnlDB.PermanentJournal.
  • The NO FALLBACK option indicates that the new table is to be nonfallback on the target system, even if it was a fallback table on the archived system.
  • If the table was nonfallback on the archive, then it retains its journaling options on the target system, that is, the journal options do not change.
  • If the table was fallback on the archive, then its images are dual on the target system.