Copying a Database to a New Database - TARA/ABU

In this example, an archived database is copied with a new name to a different Teradata Database:

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

In the example:

• The new database name is Personnel; the old database name is OldPersonnel.
• If a database named Personnel does not exist in the target system, Teradata ARC rejects the copy operation.
• The WITH JOURNAL option indicates to carry journaling over from the old Teradata Database to the new Teradata Database for any tables in the copied database that have journaling enabled on the archived system. In the example, the user copies journal images into the permanent journal table named PersonnelJnlDB.PermanentJournal. Although the tables are copied with the specified journal, the target database default does not change.
• 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 journaling options do not change.
• If the table was fallback on the archive, its images are dual on the target system.

  Although Teradata ARC copies the tables as nonfallback, the default for the target database does not change. For example, if the database named Personnel is defined with fallback, the database keeps that default after the copy operation is complete. The NO FALLBACK option applies only to the tables within the archive.