Error Logging Options
If you do not specify a value for the LIMIT option, the system defaults to a 10 error limit.
|
Syntax element … |
Specifies … |
|
LOGGING ERRORS LOGGING ALL ERRORS |
to log all data errors, reference index errors, and USI errors. If you do not specify the LOGGING ERRORS option, the system does no error handling. If an error occurs, the following session‑mode behavior occurs: The optional keyword ALL is the default. |
|
WITH NO LIMIT |
that there is no limit to the number of errors that can be logged in the error table associated with the target data table for this MERGE operation. Note that this does not mean that there is no limit on the number of errors the system can log for a MERGE request; instead, it means that errors will continue to be logged until the system-determined limit of 16,000,000 errors have been logged. See “CREATE ERROR TABLE” in SQL Data Definition Language. |
|
WITH LIMIT OF error_limit |
that the limit on the number of errors that can be logged in the error table associated with the target data table for this MERGE operation is error_limit. If this limit is exceeded, the system aborts the request in Teradata session mode or the transaction in ANSI session mode, and rolls back all changes made to the target table, but does not roll back the logged error table rows. The value you specify for error_limit can be anything in the range from 1 through 16,000,000, inclusive. The default value for error_limit is 10. |