Usage Notes - 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

The severity of any Teradata Database error code can be increased from its default severity level. The only Teradata Database error code that can be decreased from its default severity level is 2843. If a lower severity level is specified for any Teradata Database error code other than 2843, Teradata ARC displays error message ARC0124, then aborts. Specifying a Teradata Database error code's default severity level is always acceptable. See Teradata Database Error Messages for a list of selected DBS error codes and their default severity levels.

Use the DBSERROR parameter, for example, to trigger a fatal error in a situation that would normally produce a warning or a non-fatal error.

If Teradata Database error 2843 occurs, use the DBSERROR parameter to decrease the severity of the error from fatal error to warning. The error, which indicates that there is no more space available during a restore operation, will be skipped. This allows the restore operation to continue.

If a specified severity level does not match one of the values specified above for any Teradata Database error, Teradata ARC displays error message ARC0125, then aborts.

The DBSERROR parameter can be specified multiple times for the same or different Teradata Database errors. If the same DBS error is specified multiple times with the same or different severity levels, the last severity level specified will be used.