KFAA50288-E

It is not possible to restart aa....aa by resuming the previous command execution.

aa....aa: Type of processing

• Import: Data import processing

• Index-rebuild: Index rebuild processing

• Unarchive-chunk: Chunk unarchive processing

bb....bb: Cause of the error

• running authorization identifier dd....dd: The user who executed the command (authorization identifier dd....dd) is not the same as the user who executed it the previous time.

• no import status file: The command status file for the adbimport command does not exist.

• no index-rebuild status file: The command status file for the adbidxrebuild command does not exist.

• incorrect import status file: The command status file for the adbimport command is not correct.

• incorrect index-rebuild status file: The command status file for the adbidxrebuild command is not correct.

• no unarchive-chunk status file: The command status file for the adbunarchivechunk command does not exist.

• incorrect unarchive-chunk status file: The command status file for the adbunarchivechunk command is not correct.

cc....cc: Command that was suspended the previous time

• Import: adbimport command

• Index-rebuild: adbidxrebuild command

• Unarchive-chunk: adbunarchivechunk command

S:

Terminates processing.

Action:

▪ If aa....aa is Import or Index-rebuild:

• If bb....bb is running authorization identifier

  Take one of the following corrective actions:

  - If re-executing after a previous execution, ask the user who executed the command the previous time to re-execute the command. If the user who executed the command the previous time (HADB user) has already been deleted, create an HADB user with the same authorization identifier and password, and re-grant access privileges for the table.

  - As another user who has REBUILD INDEX privilege for the target table, execute the adbidxrebuild command with the --force option specified. If the suspended command is the adbimport command with background import applied (-b option specified), executing the adbidxrebuild command with the --force option deletes stored information for table data that was being processed by the adbimport command. In this case, wait for the adbidxrebuild command to complete, and then re-execute the suspended adbimport command with the -b option specified.

• If bb....bb is other than the above

  Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, execute the adbidxrebuild command with the --force option specified. If the suspended command is the adbimport command with background import applied (-b option specified) , executing the adbidxrebuild command with the --force option deletes stored information for table data that was being processed by the adbimport command. In this case, wait for the adbidxrebuild command to complete, and then re-execute the suspended adbimport command with the -b option specified.

■ If aa....aa is Unarchive-chunk:

• If bb....bb is running authorization identifier

  Take one of the following corrective actions:

  - To resume the previous command execution, ask the user who executed the command the previous time to re-execute the command. If the user who executed the command the previous time (HADB user) has already been deleted, create an HADB user with the same authorization identifier and password, and re-grant access privileges for the table.

  - As another user who has UNARCHIVE CHUNK privilege for the target table, execute the adbunarchivechunk command with the --force option specified.

• If bb....bb is other than the above

  Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, execute the adbunarchivechunk command with the --force option specified.