Partial reorganization

General considerations for a partial reorganization

The following general considerations apply when you are performing a partial reorganization:

• Full table space reorganizations rebuild and reorganize all indexes. However, when you perform a partial table space reorganization, REORG PLUS does not rebuild the nonpartitioned indexes. Instead, it updates the RID entries only for keys that are associated with the rows of the partitions that you are reorganizing.
• Because REORG PLUS does not rebuild indexes during a partial reorganization, the following restrictions apply:
  • REORG PLUS cannot update a row change time stamp column when a row is modified if the column that is implicitly updated is part of a nonpartitioned index key.
  • REORG PLUS cannot convert the RBA or LRSN format of a nonpartitioned index.
  • REORG PLUS does not collect statistics for nonpartitioned indexes.
• You cannot run two or more partial table space reorganization jobs concurrently if nonpartitioned indexes exist.
• When pending definition changes exist on the object, REORG PLUS functions as follows:
  • For pending limit key changes when both of the following conditions exist, REORG PLUS invokes DSNUTILB:
    • You are reorganizing more than one but not all partitions of a table space.
    • The pending limit key change is the only pending change.
  • For all other pending changes, REORG PLUS completes the reorganization but does not materialize the changes.

SHRLEVEL NONE considerations for a partial reorganization

In addition to the general considerations for a partial reorganization, the following considerations apply when SHRLEVEL NONE is in effect:

• REORG PLUS stops and starts only those partitions specified with the PART option of the REORG command. REORG PLUS stops or starts nonpartitioned indexes in their entirety.
• If a failure occurs after REORG PLUS starts updating one of the following indexes, you can restart the reorganization, but the index will be left in RBDP status after the restarted job completes:
  • A compressed, non-unique, nonpartitioned index

  • A document ID index for which REORG PLUS has generated document ID values

    This situation might occur if the job is the first reorganization after adding the first XML column to the table.

SHRLEVEL REFERENCE or SHRLEVEL CHANGE considerations for a partial reorganization

In addition to the general considerations for a partial reorganization, the following considerations apply when you specify SHRLEVEL REFERENCE or SHRLEVEL CHANGE:

• If nonpartitioned indexes are defined, REORG PLUS copies the original nonpartitioned indexes to the staging data sets during the UNLOAD or REORG phase.
• If you specify UNLOAD PAUSE with SHRLEVEL REFERENCE, REORG PLUS copies the indexes during the RELOAD phase, after the restart.