KFAA40205-E

An error occurred in I/O involving a file.

aa....aa: Reason the error occurred

Details are shown in the following table.

Value of aa....aa	Description
File-lock	The affected file is in use by another program. Wait until the file operations of the other program have terminated, and then retry the operation.
Invalid-parameter	An internal processing conflict was found. Contact the customer support center.
Invalid-path	The following are possible causes: The path name is invalid. Check for problems with the path name. An operation such as a delete or update was performed on the file while an application program was executing.
Invalid-permission	The following are possible causes: The permission (for access) for the specified file is invalid. Carefully review the permissions for possible problems. The file specified at the write destination is a read-only file. Check whether the write destination file is correct. A file already opened by another application program was specified.
File-format	The following are possible causes: The specified file format differs from the actual file format. If the row length (length to the linefeed) actually input from a file is longer than the input file row length calculated from the specified option values, this error might result. Suppose that the file format of the input data file is CSV format and the -r option (column structure information file) is specified for the adbimport command, the maximum value for field data number can be specified for this option. In this case, the maximum field data number specified for the column structure information option is added to the input file row length calculated from the option specification. The format of the file that specifies the table name or index identifier is invalid.
File-sequence	The multivolume file sequence is invalid.
Invalid-device	The entry type (attribute) of the specified file is invalid. If the entry type can be identified, it is displayed as a single alphabetic character in parentheses. Carefully review whether the locations where the directory name and file name were specified are correct.
No-file	There is no file to read. Another possibility is that the file was deleted during writing.
No-space	There is not enough space in the file to be written to.
No swap-file	There is no swap file for the multivolume file. Carefully review the capacity. Alternatively, specify a multivolume file.
Same-file	The file specified as the multivolume file is the same as the file just processed. Another possibility is that an attempt was made, when writing to a multivolume file, to overwrite the current volume onto a previous volume.
Unmatch-entry	The entry in the header does not match the specification of the control information file, for a file that has a header. The name of the entry that does not match is displayed in parentheses.
no-data	The quantity of data items that were recorded at the synchronization point does not exist in the specified file.

bb....bb: Name of system call in which the error occurred

The name of the system call is displayed when the OS detects an error. Otherwise, *** is displayed.

cc....cc:

Error number

dd....dd:

The source file name and row number where the failure was detected.

S:

Terminates processing.

Action:

Based on the reason the error was generated, the system call name, and the error number, eliminate the cause of the error. Then, re-execute the command.

If necessary, restore the database before re-executing the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

For details about what action to take for each error cause, see Troubleshooting in the HADB Setup and Operation Guide. If this message is output during command execution, also see Command-related problems in the HADB Setup and Operation Guide.

If using the multi-node function:

For details about the corrective action to take if a running command is interrupted and the table to be processed becomes non-updatable, see the following: Releasing a base table from non-updatable status (when the multi-node function is being used) in Base table operations (when the multi-node function is being used) in the HADB Setup and Operation Guide.