Space announcement This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Recovering the Db2 object after terminating or canceling a reorganization

(BMC.DB2.SPE2407)

Important

If you are running REORG PLUS with ENBLUTXX=YES, after an unsuccessful reorganization, the objects being reorganized might be in UTxx status. To correct this issue, restart the reorganization with RESTART or TERM. If you are not restarting the reorganization, you might need to reset the status of those objects. For more information, see Backing-out-the-reorganization.

Related topic

Running-REORG-PLUS-jobs

After you terminate or cancel a reorganization job, you might need to perform steps to recover your Db2 objects.

The following table lists the recovery steps for each phase and SHRLEVEL specification.

If REORG PLUS dynamically allocated your data sets, (by using the DDTYPE command option or through installation options), manually delete the data sets.

Phase in which you terminated or canceled the job

SHRLEVEL specified

Recovery steps

UTILINIT or UNLOAD

Any

All objects are usable and no additional steps are required.

Important

If you have not specified DELETEFILES=YES and you cancel a SHRLEVEL CHANGE reorganization, data sets and staging data sets might remain allocated. If you do not plan to restart the utility, manually delete the data sets and work files, if necessary.

DSNUTILB

SHRLEVEL NONE, SHRLEVEL REFERENCE, or SHRLEVEL CHANGE

For information about any recovery required, see the appropriate IBM Db2 documentation.

Terminated in RELOAD or REORG

SHRLEVEL NONE or SHRLEVEL REFERENCE UNLOADONLY

Recover any unusable objects.1

SHRLEVEL REFERENCE or SHRLEVEL CHANGE

Restart the objects in their original statuses to make them usable.

Canceled in RELOAD or REORG

SHRLEVEL NONE or SHRLEVEL REFERENCE UNLOADONLY

  • If you want the ability to restart the job, reset the STATUS column in the BMCUTIL table to S (for Stopped), then restart the job.
  • If you do not plan to restart the job, recover any unusable objects.1 

SHRLEVEL REFERENCE or SHRLEVEL CHANGE

Restart the objects in their original statuses to make them usable.

UTILTERM

SHRLEVEL NONE or SHRLEVEL REFERENCE UNLOADONLY

All objects are usable and no additional steps are required.

SHRLEVEL REFERENCE or SHRLEVEL CHANGE

We recommend that you restart your job rather than attempting to rename the staging data sets manually.

1 Use the highest log RBA or LRSN listed in message BMC51281I or BMC51282I to recover TORBA. For its method of specifying the RBA or LRSN value when performing a RECOVER TORBA, see the documentation for your recovery software. 


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*