Table-Level Exclude Errors - 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

The following error messages can occur when using the table-level exclude object option in an ARCHIVE statement.

ARC0106: “User excluded table(s) (%s) does/do not belong to database %s”

One or more tables specified in the EXCLUDE TABLES object option do not belong to the database object.

This is only a warning. No action is required; the archival will continue.

ARC0107: “%s is a %s. Not excluded.”

Views, macros, stored procedures, and triggers are not allowed in the EXCLUDE TABLE list. Only tables are allowed in the EXCLUDE TABLE list. Teradata ARC ignores this entry and continues the operation.

Remove the entry from the EXCLUDE TABLE list.

ARC0108: “Invalid table name in EXCLUDE TABLE list: %s.%s”

This error occurs when a table specified in EXCLUDE TABLE list does not exist in the database. Correct the table name and resubmit the job.

ARC0109: “One or more tables in EXCLUDE TABLE list for (%s) ALL is/are not valid”

This error occurs when validation of one or more tables in the EXCLUDE TABLE list failed. The invalid table names displayed prior to this error. Correct the database/table name and resubmit the job.

ARC0110: “%s is not parent database of %s in EXCLUDE TABLE list”

This error occurs when a table specified in EXCLUDE TABLE list does not belong to any of the specified parent’s child databases. Correct the database/table name and resubmit the job.

ARC0710: "Duplicate object name has been specified or the table level object belongs to one of database level objects in the list: %s"

The severity of ARC0710 has been changed to FATAL (12) from WARNING (4).

Do not specify excluded tables in a statement that also contains the database excluding them (unless using the PARTITIONS WHERE option to archive selected partitions of PPI tables, in which excluded tables are allowed). For example:

ARCHIVE DATA TABLES (db) (EXCLUDE TABLES (a)), (db.a), RELEASE LOCK, FILE=ARCHIVE; /* ARC0710 */

This fatal error resulted from one of the following:

  • the specified object is a duplicate of a previous object in the list
  • the specified object is a table level object that belongs to one of the database-level objects in the list
  • the ALL option has been specified and one of the child databases is a duplicate of an object explicitly specified in the list
  • the object name was longer than 30 characters

Remove one of the duplicate names or the table level object, or edit the length of the object name. Resubmit the script.

ARC1242 “Empty Table restored/copied: %s”

When restoring a table excluded by a user, this warning will be displayed. It normally displays during archiving for the tables that have been excluded. No data rows were restored or copied. Only the dictionary definition and the table header row were restored or copied.

This warning indicates that a table-level restore/copy must follow in order to fully restore the database.

The table is currently in restore state. Do one of the following:

  • Complete the partial restore of the database by running a table level restore/copy of the table, or
  • Access the table by running an explicit build. This results in an empty table.