KFAA41205-E

The operation on the file or directory indicated by aa....aa failed.

aa....aa:

File name or directory name

An asterisk (*) or asterisks (***) might be displayed.

bb....bb:

Name of the system call in which the error occurred

cc....cc:

Error number

S:

Terminates this transaction.

Action:

Take one of the following corrective actions:

▪ If a file name, directory name, or three asterisks (***) are displayed in place of aa....aa:

Check in the OS documentation for the system call name displayed for bb....bb and the error number displayed in place of cc....cc, and then eliminate the cause of the error. If an error occurred in a symbolic link file, check the link target files in addition to that file.

• If this message is output when starting the HADB server in a multi-node configuration or when adding a worker node to a multi-node configuration

  Check whether an error occurred during open processing of the DB area file.

  • The file name displayed for aa....aa is the symbolic link name for the DB area file.

  • The system call name displayed for bb....bb is open.

  • The error number displayed for cc....cc is ENOENT.

  If all the above conditions exist, an error occurred during open processing of the DB area file. In this case, the DB directory of the node that output this message is an invalid status. If this message is output when starting the HADB server in a multi-node configuration, execute the adbinit command on the secondary node where this message was output to recreate the DB directory, and then start the multi-node configuration HADB server normally. If this message appears when adding a worker node to a multi-node configuration, execute the adbinit command on the worker node where this message appears to recreate the DB directory, then start the HADB server on the worker node with the adbstart command and add the worker node to the multi-node configuration. For details, see the following section in the HADB Setup and Operation Guide.

  • Adding, deleting, or expanding data DB areas (when the multi-node function is being used)

  • If you cannot start a multi-node configuration HADB server normally in Problems related to starting or stopping a multi-node configuration HADB server

• If this message is output when you use the table function derived table or access an archivable multi-chunk table

  Check the existence of the file or directory indicated by aa....aa.

• If this message is output during execution of a command

  See Problems related to commands in the HADB Setup and Operation Guide.

• If the file name displayed in aa....aa is a cache file or a reuse information file

  In addition to the cache file or reuse information file displayed in aa....aa, also check the cache file storage directory and the file system status.

• If the system call name displayed in bb....bb is write or aio_write, and the error number displayed in cc....cc is 0

  There is a possibility that the writing has been interrupted by aa....aa, so re-execute the operation. As a result, if the same error occurs, it is due to insufficient disk space, so make sure there is enough free space in the area where aa....aa is located.

• If the error number displayed for cc....cc is EIO

  An error occurred in I/O involving a file. If a file name has been output, make sure that you can access the file system or disk where the file is stored.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

▪ If an asterisk (*) is displayed in place of aa....aa:

• If this message was issued while the adbimport command was executing

  Specify a smaller value in the import option adb_import_buff_blk_num.

• If this message was issued while the adbidxrebuild command was executing

  Specify a smaller value in the index rebuild option adb_idxrebuild_buff_blk_num.

• If this message was issued while the adbexport command was executing

  Specify a smaller value in the export option adb_export_wrktbl_blk_num.

• If this message was issued while the adbmergechunk command was executing

  Specify a smaller value in the merge chunk option adb_mergechunk_buff_blk_num.

• If this message was issued while the adbunarchivechunk command was executing

  Specify a smaller value in the unarchived chunk option adb_unarcv_buff_blk_num.

• If this message was issued while an SQL statement was executing

  Specify a smaller value in the client definition's adb_dbbuff_wrktbl_clt_blk_num operand.