Hitachi

Hitachi Advanced Database Messages


KFAA50246-E

The index record file is illegal. (file = aa....aa, reason = bb....bb) (errno = cc....cc) (M)

Index record file aa....aa is invalid. The cause is indicated by bb....bb.

aa....aa:

Name of index record file being created by the HADB server

bb....bb: Reason code

The following table provides details.

Value of bb....bb

Description

Duplicated-entry

During specification of multiple files, the same file was specified more than once.

Invalid-device

The file format is invalid.

Invalid-header

The header ID does not exist.

Invalid-permission

The permissions (for access) for the file are invalid.

Invalid-record-length

During specification of multiple files, the files had different record lengths.

No-file

The file does not exist.

No-header

The header does not exist.

Other-access-error

An access system call error other than Invalid-permission and No-file occurred.

cc....cc: Error number for the access system call

This is displayed if the reason code is other than Invalid-permission, No-file, or Other-access-error. For other cases, (errno = cc....cc) is not displayed.

S:

Terminates processing.

Action:

Because the index record file is corrupted, it is necessary to re-execute 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.

If Other-access-error is displayed for the reason code, check the error number for the access system call in the OS documentation, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If using the multi-node function:

For details about the corrective action to take if the adbimport, adbidxrebuild, or adbunarchivechunk command terminates abnormally 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.