DBSERROR - TARA/ABU

Teradata Archive/Recovery Utility Reference

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

DBSERROR

Purpose  

The DBSERROR parameter changes the severity of Teradata Database error codes.

Syntax  

where

 

Syntax Element

Definition

code

Teradata Database error code

level

Specifies the new severity level for the specified error code

Teradata ARC only accepts the integer values listed below for the severity level for the DBSERROR parameter:

0 = normal exit

4 = warning

8 = non-fatal error

12 = fatal error

16 = internal error (fatal)

Usage Notes  

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 Table 17 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.

Example  

ARCMAIN DBSERROR=(2805,12)

In this example, error code 2805 (maximum row length exceeded) has its severity level increased from its default level of warning (4) to fatal error (12).

ARCMAIN DBSERROR=(2843,4)

In this example, error code 2843 (database out of space) has its severity level decreased from its default level of fatal error (12) to warning (4).

ARCMAIN DBSERROR=(2843,4) DBSERROR=(2805,8)

In this example, error code 2843 (database out of space) has its severity level decreased from its default level of fatal error (12) to warning (4) and error code 2805 (maximum row length exceeded) has its severity level increased from its default level of warning (4) to non-fatal error (8).

ARCMAIN DBSERROR=(2805,4) DBSERROR=(2805,12) DBSERROR=(2805,8). 

In this example, error code 2805 (maximum row length exceeded) is specified 3 times, each with a different severity level. Changing from its default level of warning (4) to fatal error (12) to non-fatal error (8). Since non-fatal error(8) is the last severity level specified, it will be the severity level used.