Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see REORG PLUS for DB2 13.1.

Recovering from a failure

This topic provides instructions for recovering after a reorganization job fails.

The first column in the following table identifies the processing phases and, if applicable, the type of processing within the phase. The second column provides the steps to take when a reorganization job fails during that stage of processing.

Phase in which job fails

Recovery steps

UTILINIT

  1. Resubmit the job.

ANALYZE

  1. Correct the problem that caused the failure and restart the job with RESTART.

UNLOAD

  1. Correct the problem that caused the failure.
  2. Restart or resubmit the job:
    • For SHRLEVEL CHANGE, resubmit the job.
    • For SHRLEVEL NONE or SHRLEVEL REFERENCE, restart the job with RESTART.

RELOAD - redefinition of VSAM data sets, reload and index build processing

  1. Correct the problem that caused the failure
  2. If the IDCAMS DEFINE failed, manually define the data set.
  3. Restart or resubmit the job:
    • For SHRLEVEL CHANGE, resubmit the job.
    • For SHRLEVEL NONE or SHRLEVEL REFERENCE, restart the job. If you want to start your job at the beginning of the RELOAD phase, specify RESTART(PHASE), otherwise restart the job with RESTART.

RELOAD - copy processing

  1. Correct the problem that caused the failure.
  2. Restart or resubmit the job:
    • For SHRLEVEL CHANGE, resubmit the job.
    • For SHRLEVEL NONE or SHRLEVEL REFERENCE, restart the job with RESTART.

REORG

  1. Correct the problem that caused the failure.
  2. Restart or resubmit the job:
    • For SHRLEVEL CHANGE, resubmit the job.
    • For SHRLEVEL REFERENCE, restart the job with RESTART.
    • For SHRLEVEL NONE, take the appropriate action:
      • If you specified a SYSREC data set for a table space reorganization, or a SYSUT1 data set for an index reorganization, restart the job with RESTART.

      • If you did not specify a SYSREC data set for a table space reorganization, or a SYSUT1 data set for an index reorganization, and if REORG PLUS did not dynamically allocate these data sets, you will probably not be able to restart the job, but you can attempt to do so with RESTART.

        If you receive message BMC50009S indicating that REORG PLUS is unable to restart, recover any objects in recovery pending state, manually delete any dynamically allocated data sets, and resubmit the job.

LOGAPPLY

  1. Resubmit the job.

LOGFINAL

  1. Resubmit the job.

UTILTERM

  1. Correct the problem that caused the failure.
  2. Restart the job with RESTART.

If you cannot restart the job, see Managing-a-reorganization-that-does-not-complete-in-the-UTILTERM-phase for SHRLEVEL REFERENCE and SHRLEVEL CHANGE.

For SHRLEVEL CHANGE, REORG PLUS backs out the reorganization and leaves the spaces in their original statuses when either of the following conditions exists:

  • The failure occurred while REORG PLUS was setting restrictive statuses and conditions exist that might cause a restarted reorganization to create invalid indexes.
  • You are reorganizing a catalog object and the failure occurred during rename processing.

Related topic

Running-REORG-PLUS-jobs

 

 

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