DB2 Version 9.7 for Linux, UNIX, and Windows

Restarting or terminating an ALLOW READ ACCESS load operation

An interrupted or cancelled load operation that specifies the ALLOW READ ACCESS option can also be restarted or terminated using the ALLOW READ ACCESS option. Using the ALLOW READ ACCESS option allows other applications to query the table data while the terminate or restart operation is in progress. As with a load operation in ALLOW READ ACCESS mode, the table is locked exclusively prior to the data being committed.

About this task

If the index object is unavailable or marked invalid, a load restart or terminate operation in ALLOW READ ACCESS mode is not permitted.

If the original load operation is interrupted or cancelled in the index copy phase, a restart operation in the ALLOW READ ACCESS mode is not permitted because the index might be corrupted.

If a load operation in ALLOW READ ACCESS mode is interrupted or cancelled in the load phase, it restarts in the load phase. If it is interrupted or cancelled in any phase other than the load phase, it restarts in the build phase. If the original load operation is in ALLOW NO ACCESS mode, a restart operation occurs in the delete phase if the original load operation reaches that point and the index is valid. If the index is marked invalid, the load utility restarts the load operation from the build phase.

Note: All load restart operations choose the REBUILD indexing mode even if the INDEXING MODE INCREMENTAL option is specified.

Issuing a LOAD TERMINATE command generally causes the interrupted or cancelled load operation to be rolled back with minimal delay. However, when issuing a LOAD TERMINATE command for a load operation where ALLOW READ ACCESS and INDEXING MODE INCREMENTAL are specified, there might be a delay while the load utility scans the indexes and corrects any inconsistencies. The length of this delay depends on the size of the indexes and occurs whether or not the ALLOW READ ACCESS option is specified for the load terminate operation. The delay does not occur if the original load operation failed prior to the build phase.

Note: The delay resulting from corrections to inconsistencies in the index is considerably less than the delay caused by marking the indexes as invalid and rebuilding them.

A load restart operation cannot be undertaken on a table that is in the Not Load Restartable table state. A table can be placed in the Not Load Restartable table state during a rollforward operation. This can occur if you roll forward to a point in time that is prior to the end of a load operation, or if you roll forward through an interrupted or cancelled load operation but do not roll forward to the end of the load terminate or load restart operation.