Recovering the Db2 object after terminating or canceling a LOADPLUS job

You must perform certain recovery steps when any of the following conditions exist:

You terminated the job by
- Specifying the TERM parameter on the EXEC statement
- Deleting the row from the BMCUTIL table that corresponds to the utility job
The job ended for a reason other than you terminating it, and you do not intend to restart it (or you cannot restart it due to omitted SORTOUT or SYSUT1 data sets).
You canceled the job, and you do not intend to restart it (or you cannot restart it due to omitted SORTOUT or SYSUT1 data sets).

Related topics

The following table describes the recovery steps that you need to take.

Important

If you canceled your LOADPLUS job, or the job ended for a reason other than you terminating it, you can usually restart the job. When you restart the job, you do not normally need to perform any additional recovery steps. However, for information about special restart conditions, see Restarting-LOADPLUS.

Recovering after termination

Phase in which job terminated	Specified options	Other conditions	Is object usable?	Recovery steps
Any phase other than UTILTERM	SHRLEVEL REFERENCE or LOAD REPLACE SHRLEVEL CHANGE or LOAD RESUME YES SHRLEVEL CHANGE PART n REPLACE		The object is usable (with original data).	No recovery steps are required.
UTILINIT	Any		The object is usable.	No recovery steps are required.
DSNUTILB	Any		The object might be usable.	For information about any recovery required, see the appropriate IBM DB2 documentation.
PRELOAD	LOAD REPLACE		The object is usable.	No recovery steps are required.
PRELOAD	Any option other than LOAD REPLACE		The object is usable.	Start the table space and index spaces.
LOAD	LOAD RESUME YES SHRLEVEL NONE with one of the following specifications: No PART specifications and no TABLE tableName REPLACE specification One or more PART specifications without REPLACE	The table space contains data before the load job.	The object is not usable.	Complete the following steps: Start the table space and index spaces. Recover the table space. Recover the indexes. Rerun the job.
LOAD	LOAD RESUME YES SHRLEVEL NONE PART n REPLACE		The object is not usable.	Complete the following steps: Start the table and index spaces. Recover the partition. Recover the corresponding partitions of the partitioned indexes and all nonpartitioned indexes. Rerun the job.
LOAD or COMBINED	LOAD RESUME YES INTO TABLE tableName REPLACE		The object is not usable.	Complete the following steps: Start the table and index spaces. Either rerun the job or recover the table space and then recover the indexes.
LOAD or COMBINED	LOAD REPLACE SHRLEVEL NONE		The object is not usable.	Complete the following steps: Start the table and index spaces. Either rerun the job or recover the table space and then recover the indexes.
COMBINED	LOAD RESUME YES SHRLEVEL NONE, single-phase		The object is not usable.	Complete the following steps: Start the table and index spaces. Recover the table space and then recover the indexes. Rerun the job.
LOAD or COMBINED	SHRLEVEL NONE or LOAD RESUME YES SHRLEVEL CHANGE SQLAPPLY or LOAD RESUME YES SHRLEVEL CHANGE without PART n REPLACE	The table space has been loaded and all discard processing has completed.	It might be only the indexes that are not usable.	Complete the following steps: Determine whether the table space was loaded by checking message BMC51475I or by querying the BMCSYNC table. Start the table and index spaces. Recover the indexes. (You must perform this last step before you can use any of the loaded data.)
UTILTERM	SHRLEVEL NONE or LOAD RESUME YES SHRLEVEL CHANGE SQLAPPLY or LOAD RESUME YES SHRLEVEL CHANGE without PART n REPLACE		The object is usable.	No recovery steps are required.
UTILTERM	SHRLEVEL REFERENCE or LOAD REPLACE SHRLEVEL CHANGE or LOAD RESUME YES SHRLEVEL CHANGE PART n REPLACE	The rename or FASTSWITCH process started but did not complete.	The object is not usable.	Manually complete or back out the rename or FASTSWITCH process and remove pending statuses. Note: We strongly recommend that you restart your job rather than attempt to rename the staging data sets manually.

Recovering the Db2 object after terminating or canceling a LOADPLUS job

On this page