Most errors are fatal, resulting in termination of Teradata TPump. The exceptions to this general rule are as follows:
- User-specified SQL commands fail with no adverse effect. The variable &SYSRC is set, and if the script tests this variable it can stop the job if necessary.
- Data-related errors in the database can reach the user-specified error limit before terminating the job. Beginning with Teradata Tools and Utilities 14.10, RDBMS returns a list of data-related error codes:
- When the user does not have permission on the SYSLIB.DBSDATARELATEDERRORS view, TPump displays the database “no permission” message and an information message that the internal list of data-related errors will be used for the job, and sets the job's return code to four (assuming there are no other errors for the rest of the job).
- For any other database errors in which the database did not restart, TPump displays the database error message and an information message that the internal list of data-related errors will be used for the job, and the job's return code remains unchanged.
- In the rare instance that zero rows are returned from the SYSLIB.DBSDATARELATEDERRORS view, TPump displays an information message that zero rows were returned and that the internal list of data-related errors will be used for the job, and the job's return code remains unchanged.
- When one or more rows are returned from the SYSLIB.DBSDATARELATEDERRORS view, TPump does not display any information about the DBS data-related error view and the job's return code remains unchanged. For the detailed information regarding the list of data-related errors codes, see Teradata Vantage™ - Database Utilities, B035-1102.