KFAA30959-E

An error occurred in processing on a directory or one of the following files. <SQLSTATE: 40528>

• DB area file

• System file

• Directory

• CSV file that will be the input data file of the ADB_CSVREAD function

• Audit trail file that will be the input data of the ADB_AUDITREAD function

• File used for synonym search (synonym list definition file, dictionary creation file, dictionary deletion file, synonym dictionary file, or temporary work file)

aa....aa:

Name of invalid system call

bb....bb:

Error number or 0

cc....cc:

File name or asterisk (* or ***)

S:

Invalidates this transaction.

Action:

Take one of the following corrective actions:

●If a file name or three asterisks (***) is displayed in place of cc....cc

• If bb....bb is not 0

  In the OS documentation, check the system call name indicated by aa....aa and the error number indicated by bb....bb, and then eliminate the cause of the error.

  If aa....aa is aio_read, also check system call read. If aa....aa is aio_write, also check system call write.

  If an error occurred in a symbolic link file, check the link target files in addition to that file.

  For details about how to take action for each cause of the error, 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 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 a KFAA41200-E message was output immediately prior to this message, carefully review the settings of the file displayed in place of cc....cc.

• If bb....bb is 0

  Re-execute the transaction. If re-executing the transaction results in the same error, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If this message is output during execution of an SQL statement with the scalar function CONTAINS (with the synonym-search specification) specified, check whether a file name that begins with a synonym dictionary name is displayed for cc....cc. If a file name that begins with a synonym dictionary name is displayed, the synonym dictionary file might not exist. Check in the OS documentation for the system call name and error number that are displayed. If the error is caused by the absence of a synonym dictionary file, re-register the synonym dictionary and re-create the synonym dictionary file.

● If an asterisk (*) is displayed in place of cc....cc

Check and, if necessary, revise the aio_max_nr kernel parameter value by referencing Estimating the kernel parameters in the HADB Setup and Operation Guide. Alternatively, check and, if necessary, revise the following settings:

• 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

  Reduce the value of the adb_idxrebuild_buff_blk_num index rebuild option.

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

  Reduce the value of the adb_export_wrktbl_blk_num export option.

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

  Reduce the value of the adb_mergechunk_buff_blk_num merge chunk option.

• 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.