The system outputs a logical error number indicating the cause of an error to the error information file. This logical error number (XX) corresponds to the KFPL310XX message.
Table 5-25 shows lists and explains the logical error numbers for logical errors.
Table 5-25 Logical error numbers and descriptions
Logical error number | Description of logical error |
---|---|
1 | Input data for NCHAR or NVARCHAR is invalid:
|
2 |
|
3 | The length of variable-length data (VARCHAR, NVARCHAR, MVARCHAR, BLOB, or BINARY) is invalid. |
4 | Data conversion error occurred. |
5 |
|
6 | Null value was specified for a table or column for which null value is prohibited:
|
7 | Input records are not sorted by the cluster key. |
8 | For a table for which a cluster key or index has been defined, the following error occurred:
|
9 | A column value was found that did not satisfy the partitioning conditions for the table created (being processed). |
10 | The row length of binary-format input data is invalid. |
11 | The LOB data is invalid:
|
12 | The specified LOB input file was not found. A file other than a regulator file was specified for a LOB input file. |
13 | The length of the LOB data exceeds the defined length. |
14 | There is a contradiction between the specifications of the LOB column structure base table and the specifications in the LOB input file:
|
15 | The numbers of data items do not match between the LOB column structure base table and the LOB column input file. |
16 | Invalid parameter for a constructor function |
17 | No access privilege for LOB input file |
18 | Invalid data format for storage in abstract data type |
19 | Invalid number of data elements for storage in repetition column |
20 | There is an enclosing character at an invalid location. |
90 | The input data is longer than the defined column length.
|