Default language.

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.

General rebalancing considerations

The following general restrictions and considerations apply to partition rebalancing:

  • When multiple limit key change requests exist for a reorganization, REORG PLUS materializes only the first changes that it finds based on the following hierarchy:
    • Pending limit key alters on the object
    • ALTER statements in a DDLIN data set included in your JCL
    • Limit key changes as a result of the REBALANCE option specified on your REORG command

Related topics

Partition rebalancing

Rebalancing partitions

  • REORG PLUS processes all related partitions in the same unload task. Consequently, the task distribution might not be as even as in a normal reorganization.
  • You can rebalance up to 255 ranges of logically contiguous partitions in a single execution of REORG PLUS.
  • With SHRLEVEL CHANGE, you can use the DDLOUT DD statement to obtain only a report (without completing the reorganization) of the ALTER statements that REORG PLUS would use to rebalance partitions. For more information, see  DDLOUT data sets.
  • REORG PLUS changes the following options:
    • CPYRFAIL=TERM to COPYPEND
    • FSFALLBACK YES to NO
    • INVALIDATECACHE=NO to YES
    • UPDATEDB2STATS NO to YES when INVALIDATECACHE=NO

  • When a failure occurs while processing limit key updates, REORG PLUS always terminates, and Db2 rolls back the limit key updates. Depending on other conditions of the job, REORG PLUS completes one of the following processes:

    • Backs out any other changes made by the reorganization
    • Abends, leaving the object in RECP status

 

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