Restart of LOAD
You can restart a LOAD utility job.
You can restart the job either at its last commit point (RESTART(CURRENT)) or at the beginning of the phase during which operation ceased (RESTART(PHASE)). LOAD output messages identify the completed phases. Use the DISPLAY command to identify the specific phase during which operation stopped.
By default, DB2® uses RESTART(CURRENT), except if LOAD is restarting during the UTILINIT phase or the UTILTERM phase. In both of these situations, DB2 uses RESTART(PHASE) by default. You can override the default RESTART values by using the RESTART parameter.
- If LOAD abnormally terminates or a system failure occurs while LOAD is in the UTILTERM phase, you must restart with RESTART(PHASE).
- If you restart a LOAD job with the RESUME YES and SORTKEYS NO options for a table that has LOB columns, you must use RESTART(CURRENT).
- If you use RESTART(PHASE) to restart a LOAD job that specified RESUME NO, the LOB table spaces and indexes on auxiliary tables are reset.
- For a table that has LOB columns, you cannot restart a LOAD job that uses the INCURSOR option.
- If you restart a LOAD job that uses the STATISTICS keyword, inline statistics collection does not occur. To update catalog statistics, run the RUNSTATS utility after the restarted LOAD job completes.
- If you are using a BatchPipes® file, you cannot restart the LOAD utility. If the application that populates the BatchPipes file terminates, you need to terminate the job where LOAD is running. If the LOAD utility was invoked from a stored procedure, you also need to terminate the WLM application environment of the LOAD utility that reads the BatchPipes file. After you terminate the job, terminate the LOAD utility by using the DB2 TERM UTILITY command, and then you can resubmit the LOAD job.
- You cannot restart LOAD with RESUME and with
PRESORTED YES in the RELOAD phase. If you do so, utility processing
abnormally terminates, and LOAD issues an error message. You must:
- Terminate LOAD
- Recover the table space that is being loaded
- Recover all indexes on the table space that are in the REBUILD-pending state
The following table provides information about restarting LOAD, depending on the phase that LOAD was in when the job stopped. The TYPE column distinguishes between the effects of specifying RESTART or RESTART(PHASE). Additional phase restrictions are explained in the notes.
Phase | Type of RESTART | Required data sets | Notes |
---|---|---|---|
RELOAD | CURRENT | SYSREC and SYSUT1 SYSMAP and SYSERR | 1, 2, 10 |
PHASE | SYSREC | 3, 10, 11 | |
SORT | CURRENT | SYSUT1 | 4, 10 |
PHASE | SYSUT1 | 10 | |
BUILD | CURRENT | SORTOUT | 4, 5, 10 |
PHASE | SORTOUT | 5, 10 | |
SORTBLD | CURRENT | SYSUT1 and SORTOUT | 5, 6, 10 |
PHASE | SYSUT1 and SORTOUT | 5, 6, 10 | |
INDEXVAL | CURRENT | SYSERR or SYSUT1 | 2 |
PHASE | SYSERR or SYSUT1 | 2 | |
ENFORCE | CURRENT | SORTOUT and SYSUT1 | 7 |
PHASE | SORTOUT and SYSUT1 | 7 | |
DISCARD | CURRENT | SYSMAP and SYSERR SORTOUT and SYSUT1 | 7, 8 |
PHASE | SYSMAP and SYSERR SORTOUT and SYSUT1 | 7, 8 | |
REPORT | CURRENT | SYSERR or SORTOUT SYSMAP and SYSERR | 7, 9 |
PHASE | SYSERR or SORTOUT SYSMAP and SYSERR | 7, 9 | |
Note:
|