16.20 - User Data Restoration Commands - Teradata Vantage NewSQL Engine

Teradata Vantageā„¢ NewSQL Engine Node Software Migration Guide

prodname
Teradata Database
Teradata Vantage NewSQL Engine
vrm_release
16.20
created_date
March 2019
category
Administration
Configuration
Installation
featnum
B035-5942-162K

The following table provides some examples of the commands that might be included in your restore job scripts. These are only the ARC commands and are not complete scripts.

You must revalidate referential constraints.
Example Commands
If you have permanent journals, re-create the journal dictionaries using these commands that exclude database DBC. The journal data is not restored. RESTORE DICTIONARY TABLES ALL FROM ARCHIVE,

RELEASE LOCK,

FILE=JNLARCH:

Commands to restore all user databases except those specifically excluded.
If migrating from a Teradata Database release earlier than 15.0, do not include TD_SERVER_DB among the excluded databases.

These commands restore user databases, secondary indexes, and fallback.

RESTORE DATA TABLES (DBC) ALL,

EXCLUDE(DBC), (TD_SYSFNLIB), (CRASHDUMPS), (SYSLIB), (SYSSPATIAL), (TD_SERVER_DB),

RELEASE LOCK,

FILES=ARCHIVE;

Command to restore TD_SERVER_DB alone after restoring other user data. RESTORE DATA TABLES (DBC), (TD_SERVER_DB),

EXCLUDE (DBC),

RELEASE LOCK,

FILES=ARCHIVE;

Release the host utility locks with this command. RELEASE LOCK (DBC) ALL;
You must revalidate referential constraints with these commands. REVALIDATE REFERENCES FOR (DBC) ALL,

EXCLUDE (DBC), (TD_SYSFNLIB), (SYSBAR)

RELEASE LOCK;

Warning Messages

Review any warning messages resulting from the RESTORE command. Some messages may indicate that additional actions are required to complete portions of the restore. The following messages related to statistics may require recollection of statistics on the table and column(s) specified in the SQL information contained in the ARC log.
  • ARC0727 CREATE Stat Collection failed with error %s: %s.

    Explanation: An error was encountered while trying to recreate a Stat Collection. The error will include the error number and text returned by the Teradata system.

    Remedy: Either resolve the Teradata error that was displayed in the ARC log and reattempt the restore, or recollect statistics on the table and column(s) specified in the SQL information provided in the ARC log.

  • ARC0728 Stat Collection can not be recreated during a cluster restore. Stat Collections should be restored from this archive after all cluster restore and build steps have been completed.

    Explanation: During the dictionary part of a cluster restore, ARC cannot recreate stat collection information, since the data has not yet been restored to the tables. ARC must defer recreating the stat collection until after the data for all tables has been restored.

    Remedy: After the cluster restore and build steps have been completed, the user needs to manually recollect the statistics.

  • ARC0729 SHOW Stat Collection query failed with error %s: %s.

    Explanation: An error was encountered while trying to query the definition for a stat collection. The error will include the error number and text returned by the Teradata system.

    Remedy: Either resolve the Teradata error that was displayed in the ARC log and reattempt the restore, or recollect statistics on the table and column(s) specified in the SQL information provided in the ARC log.

  • ARC0730 Stat Collection query failed with error %s: %s.

    Explanation: An error was encountered while trying to query the list of SC indexes from the StatsV view in database DBC. The error will include the error number and text returned by the Teradata system.

    Remedy: Either resolve the Teradata error that was displayed in the ARC log, or recollect statistics on the table and column(s) specified in the SQL information provided in the ARC log.