37.6 Notes

1. The adbreorgsystemdata command uses three processing real threads. If the adbreorgsystemdata 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 adbreorgsystemdata command. If allocation of processing real threads is placed in wait status, see Points to consider about the number of processing real threads to be used during command execution in the HADB Setup and Operation Guide and take appropriate action.

   In addition, the number of processing real threads that can be used depends on whether the client-group facility is applied. For details, see Points to consider when specifying the number of processing real threads for a group in the HADB Setup and Operation Guide.

2. Do not perform read or write operations on unload files by using other applications while the adbreorgsystemdata command is being executed.

3. Use X'0A' (LF) or X'0D0A' (CRLF) for the line break code in any file specified in the options of the adbreorgsystemdata command.

4. Use the adbcancel command to cancel execution of the adbreorgsystemdata command. For details about how to use the adbcancel command to suspend an executing command, see 1.6 When suspending (forcibly terminating) an executing command.

5. System table reorganization processing is executed in server processes. Therefore, using the Ctrl+C keys to forcibly terminate the adbreorgsystemdata command process will not interrupt reorganization processing of system tables that is being performed by server processes (such processing continues). When the reorganization processing is complete, the KFAA81001-I message is output to the message log file.

6. Work files (temporary work files) are created temporarily during reorganization processing of system tables. If the adbreorgsystemdata command terminates normally (the return code is 0 or 4), and if deletion of pre-reorganization data fails (the return code is 12), temporary work files are deleted automatically. However, if the adbreorgsystemdata command does not terminate normally, temporary work files might not be deleted.

   At this time, if you re-execute the adbreorgsystemdata command without changing the table to be processed or the -w option, the remaining temporary work files are deleted automatically when the command terminates normally. Therefore, it is not a problem if temporary work files remain. However, if you want to increase free disk space before re-executing the adbreorgsystemdata command, delete the temporary work files.

7. During the reorganization processing of system tables, files (unload files) are created temporarily to store the data of system tables with the invalid row data removed. If the adbreorgsystemdata command terminates normally (the return code is 0 or 4), and deletion of the pre-reorganization data fails (the return code is 12), the unload files are deleted automatically. However, if the adbreorgsystemdata command does not terminate normally, unload files might not be deleted.

   At this time, if you re-execute the adbreorgsystemdata command without changing the table to be processed or the -f option, the remaining unload files are deleted automatically when the command terminates normally. Therefore, it is not a problem if unload files remain.

   If you change the -f option before re-executing the adbreorgsystemdata command, check the storage directory of the unload files from before the change. If any unload files remain, delete them.

   Note that one unload file is output per table to be processed. Names of unload files are written as follows.

   Unload file name

   reorganize-unload-[table-ID]-00001

   table-ID: Table ID of the table to be processed, converted to a hexadecimal number expressed as an 8-digit string

To Page Top