Notes

If RDAREA re-initialization or the PURGE TABLE statement is executed before re-execution of the database reorganization utility, the synchronization point information that was set might be lost. In such a case, the re-execution will not be treated as re-execution of reorganization with synchronization points set.
If the utility terminates abnormally during reorganization with synchronization points set for a LOB column structure base table, specify CLR when the utility is re-executed. If CLR is not specified, retrieval efficiency for the LOB column might deteriorate even after reorganization.
If names for the files listed below are not stated clearly, the database reorganization utility will create these files automatically:
- Index information file
- Error information file
If the database reorganization utility terminates abnormally, these files will remain on the disk. Because the database reorganization utility will create files under new names during re-execution, these files remaining from before the abnormal termination might cause a space shortage on the disk. Therefore, delete these files before re-execution.
If the database reorganization utility (-k rorg) terminates abnormally, the abnormal termination status is set as the status of the table. If the database reorganization utility (-k rorg) is re-executed from this status, based on the status of the table, processing restarts from the point where the abnormal termination occurred, and the status of the table is cleared when processing is finished.
If an index was created in the batch mode (-k ixmk) after the database reorganization utility terminated abnormally during index creation, the status of this table is not cleared. Therefore, if you load indexes that were created in the batch mode, change the table status by executing the database reorganization utility (-k rorg) with the tblstatus operand specified in the option control statement. If this operation is not executed, the table remains in the status it was in when the utility terminated abnormally during index creation.

20.18.4 Notes