Hitachi

Hitachi Advanced Database Messages


KFAA51272-E

An error occurred in the input data file of the system-defined function ADB_CSVREAD. (reason = aa....aa, file = bb....bb, row = cc....cc, field = dd....dd) (M)

An error occurred in the file that will be the input data of the ADB_CSVREAD function. The location of the error can be identified based on bb....bb, cc....cc, and dd....dd.

aa....aa: Cause of the error
  • DATA CONVERSION ERROR: An error occurred during file conversion processing.

  • NO FIELD: Field data does not exist.

  • INVALID ENCLOSING CHARACTER: Invalid enclosing characters exist in the data.

bb....bb:

Path name of the file in which the error occurred

cc....cc:

Row number of data in the file

dd....dd:

Field data number in the file

S:

Invalidates this transaction.

Action:

Make sure that the compression format of the file indicated by bb....bb matches the specification of the compression format option COMPRESSION_FORMAT of the ADB_CSVREAD function.

If they match, identify the field data that caused the error based on the information indicated by cc....cc and dd....dd. Then, take the corrective action for the cause of the error indicated by aa....aa.

  • If aa....aa is DATA CONVERSION ERROR

    The data type specified for the table function column list is not compatible with the data type of the field data. Correct the data type specified for the table function column list.

    If the error occurred at the end of the row, check that the row ends with a linefeed in the file indicated by bb....bb.

  • If aa....aa is NO FIELD

    Add field data.

    Alternatively, make sure that the field data number is specified correctly for the specification column option.

  • If aa....aa is INVALID ENCLOSING CHARACTER

    Correct the invalid enclosing characters.

    Alternatively, make sure that the enclosing character specification option is specified correctly.

If this message is output when you access an archivable multi-chunk table, the file indicated by bb....bb (archive file) has been corrupted. In this case, see Recovering the database from the backup in the HADB Setup and Operation Guide, and then recover the database.