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: Length of the input data is an odd value
2	The numeric or sign part of packed-format decimal numeric data is invalid. The numeric part of date, time, or time stamp data is invalid, or the length of the fraction part of time stamp data is invalid. The numeric or sign part of date interval or time interval data is invalid.
3	The length of variable-length data (VARCHAR, NVARCHAR, MVARCHAR, BLOB, or BINARY) is invalid.
4	Data conversion error occurred.
5	Input data does not match the table in terms of the number of columns. The column, not enclosed in double quotation marks ("), cannot be recognized. A null character (0x00) is found as part of data in a text (DAT format) file.
6	Null value was specified for a table or column for which null value is prohibited: Null value was specified for a table with FIX attribute. Null value was specified for a cluster key component column. Null value was specified for a column with NOT NULL attribute. Null value was specified for the primary key component column.
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: Duplicate key is prohibited, but a specified key is duplicated.
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: The length of the file name of the LOB input file is invalid that was specified in the input data file for the LOB column structure base table. Invalid LOB data length was specified for a LOB column input file or a binary-format file. An invalid EOF was detected while acquiring the 4-byte LOB data length in the LOB column input file or while acquiring the LOB data with the specified length.
12	The specified LOB input file was not found.
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: One or more bytes of data are specified for a null value specification. One or more bytes of data are specified for a default value.
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. When the lengover operand is omitted: The system discards the excess portion of the data and then stores the data. When the lengover operand is specified: The system does not store any data because it assumes an input data error.

Notes

1. If the -e option is not specified and the length of specified variable-length data is invalid, the system treats the specified data length as being invalid and skips the corresponding row data.
2. If there is an error in a binary-format input data file (excluding an input data file output by the database reorganization utility), the system outputs a dump image listing of the first erroneous input data in hexadecimal and text format (2-byte codes are ignored). The output format depends on the data that is contained, as shown below:

• For data in a BINARY-type column or abstract data-type column with the BINARY attribute
  If the data length exceeds 1,024 bytes, the system outputs the length section with a length of 4 bytes and the data section with a maximum length of 1,024 bytes from the beginning. After a linefeed, the system outputs : at the beginning and then outputs the remaining column data. The following shows an output example:
  

  

• For data in a BLOB-type column
  The data is not output.