Previous Topic: Assigning Null Values to an SQL ColumnNext Topic: Adding, Replacing, and Dropping Data on SQL Tables


How CA Culprit Handles Data Insertion Errors

During the output phase of CA Culprit, it is possible to encounter errors during the SQL bulk insert. If this occurs, CA Culprit produces a diagnostic dump of the output data record and continue processing, as shown below:

Output Phase Diagnostic Error

E C760001 THE FOLLOWING ROWS WERE NOT STORED DUE TO INSERT ERRORS:      OUTPUT                    R E C O R D    L A Y O U T      RECORD   ERROR      NUMBER   CODE       0005    1023       CHAR             .............ABCDE....                          ZONE   4444444444FFFF000130000CCCCC0000                          DIGIT  0000000000FFFF0002C0000123450000                                 1...5...10....5...20....5...30..

In the above example, the Output Record Number indicates that the fifth row being written contained an error.

The Record Layout provides a complete vertical hex dump of the CA Culprit output buffer to assist in debugging. The Error Code 1023 indicates a constraint violation. This value was obtained from the SQLCERC field in the SQL Communications Area. A list of common error codes is given below:

SQLCERC Codes(Error: Don't know what to do with column width of "10," (3).

The following is a list of the error codes and their description

1008

No storage to load data

1010

Load of Table Deadlocked

1023

Constraint Violation

1025

Data Exception

1026

Data Conversion Error

1051

Cardinality Violation

1058

Duplicate Key Violation

1067

I/O Error While Loading Table