LOGSKIPPED - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

The LOGSKIPPED parameter instructs Teradata ARC to log all of the tables that are skipped during an ARCHIVE operation.

The LOGSKIPPED parameter instructs Teradata ARC to log all of the tables that are skipped during an ARCHIVE operation. The tables are logged in a table named SkippedTables, which is created in the ARC catalog database ($ARC by default, or $NETVAULT_CATALOG when using NetVault).

Teradata ARC skips a table when the table is:

  • Currently involved in a restore operation from a different instance of Teradata ARC
  • Currently involved in a FastLoad or MultiLoad operation
  • Missing a table header or a dictionary row, or is otherwise damaged
  • For each table that is skipped, Teradata ARC adds a row in the SkippedTables table. The columns included in the SkippedTables table are:

  • EVENTNUM—Event number of the archive job where the table was skipped.
  • DATABASENAME—Database containing the skipped table.
  • TABLENAME—Name of the table that was skipped.
  • ERRORTIME—TIMESTAMP value of when the error occurred on the table.
  • ERRORCODE—Error code that caused Teradata ARC to skip the table.
  • ERRORTEXT—Error text for the corresponding error code.
  • Teradata ARC does not automatically retry tables that are added to the SkippedTables table. Therefore, ensure that these tables are separately archived when an error condition is fixed.