43.6 Notes

1. The adbunarchivechunk command can only be executed when the HADB server is running.

2. Use the adbcancel command to cancel execution of the adbunarchivechunk command. Alternatively, use a method such as the adbstop --force command or the OS's kill command to forcibly terminate the server process. For details about how to use the adbcancel command to suspend an executing command, see 1.6 When suspending (forcibly terminating) an executing command.

3. Chunk unarchive processing is performed by server processes. Therefore, using the Ctrl+C keys to forcibly terminate the adbunarchivechunk command process will not interrupt unarchiving chunks that is being performed by server processes (such processing continues). When the chunk unarchive processing is complete, the command outputs the KFAA81001-I message to the message log file.

4. If the adbunarchivechunk command is executed while another command or application program is running, HADB might not be able to allocate the required number of processing real threads. If this happens, HADB waits until the required number of processing real threads can be allocated before executing the adbunarchivechunk command. If allocation of processing real threads is placed in wait status, see the topic Points to consider about the number of processing real threads to be used during command execution in Points to consider when executing commands concurrently in Preparing Resources in the HADB Setup and Operation Guide and take appropriate action.

5. Work files (temporary work files) are created temporarily during chunk unarchive processing. If the adbunarchivechunk command terminates successfully (the return code is 0 or 4), the temporary work files are deleted automatically. However, if the adbunarchivechunk command does not terminate successfully, the files might not be deleted.

   Some of the temporary work files are needed when other commands are re-executed. For this reason, do not delete temporary work files before you re-execute other commands. If you delete them, the other commands will not execute correctly.

6. Because temporary work files might cause a shortage of disk space, we recommend that you delete temporary work files from time to time if there is no need to re-execute other commands.

   Check the following directories periodically for any remaining temporary work files and delete any that are found:

   • $DBDIR/ADBSYS/ADBUTL

   • Temporary work file storage directories specified in the -w option (or in $DBDIR/ADBWORK when the -w option was omitted)

7. Make sure that there is no duplication of the absolute paths for the directories and files specified in the adbunarchivechunk command's options. This applies to the following directories and files:

   • Temporary work file storage directories (specified in the -w option or specified in the directory path file specified in the -w option)

   • Directory path files specifying the storage locations of temporary work files (specified in the -w option)

   • Unarchive chunk option file (specified in the -z option)

   Make sure that the absolute paths of these directories and files are unique, and different from those of any directories or files used by any programs other than the adbunarchivechunk command. If there are any duplicate paths, data in the files might be lost. Also make sure that symbolic links and relative paths are specified correctly.

8. If you execute the adbunarchivechunk command with the -t option specified, chunk unarchive processing is not executed. Specify the -t option if you want to check in advance which chunks are to be unarchived, among those corresponding to the range specified in the -r option or the -c option.

   To perform chunk unarchive processing on the chunks after checking which chunks are to be unarchived, do not change any options other than the -t option, and execute the adbunarchivechunk command with the -t option omitted.

To Page Top