The second error table, called the application error table, is the one specified from the ErrorTable2 attribute. It provides information about:
- Uniqueness violations
- Field overflow on columns other than primary index fields
- Constraint errors
The following table lists, in alphabetical order, the application error table columns that can be specified.
A copy (or mirror) of the target table columns follows the DBCErrorField column in the application error table.
|ApplySeq||Sequence number assigned to the DML group in which the error occurred (the same as DMLSeq). It can be ignored in error handling.|
|DBCErrorCode||Code for the error.|
|DBCErrorField||Field name of the target table in which the error occurred.
This field may be blank if the system cannot determine which field caused the problem. Error 2677 (stack overflow) is an example of such a condition.
|DMLSeq||Sequence number assigned to the DML statement within the DML group in which the error occurred.|
|ImportSeq||Sequence number assigned to the input source in which the error occurred.|
|SourceSeq||Sequence number assigned to the row from the input source (the ImportSeq number) in which the error occurred.|
|STMTSeq||Sequence number of the DML statement within the DML group (as indicated by the previous column DMLSeq) that is executed when the error occurred.|
|Uniqueness||Value that prevents duplicate row errors in the error table. It can be ignored in error handling.|