Concurrency and compatibility for REPAIR

The REPAIR utility has certain concurrency and compatibility characteristics associated with it.

Db2 treats individual data and index partitions as distinct target objects. Utilities that operate on different partitions of the same table space or index space are compatible.

Claims

The following table lists any claims or drains that the utility acquires and any restrictive states that are set on the target object.

Table 1. Claim classes of REPAIR operations
Action Table space or partition Index or partition
REPAIR LOCATE KEY DUMP or VERIFY DW/UTRO DW/UTRO
REPAIR LOCATE KEY DELETE or REPLACE DA/UTUT DA/UTUT
REPAIR LOCATE RID DUMP or VERIFY DW/UTRO None
REPAIR LOCATE RID DELETE DA/UTUT DA/UTUT
REPAIR LOCATE RID REPLACE DA/UTUT None
REPAIR LOCATE TABLESPACE DUMP or VERIFY DW/UTRO None
REPAIR LOCATE TABLESPACE REPLACE DA/UTUT None
REPAIR LOCATE INDEX PAGE DUMP or VERIFY None DW/UTRO
REPAIR LOCATE INDEX PAGE DELETE None DA/UTUT
Legend:
  • DA - Drain all claim classes - no concurrent SQL access.
  • DW - Drain the write claim class - concurrent access for SQL readers.
  • UTUT - Utility restrictive state - exclusive control.
  • UTRO - Utility restrictive state - read-only access allowed.
  • None - Object is not affected by this utility.

REPAIR does not set a utility restrictive state if the target object is DSNDB01.SYSUTILX.

Compatibility

The following tables show which utilities can run concurrently with REPAIR on the same target object. The target object can be a table space, an index space, or a partition of a table space or index space. If compatibility depends on particular options of a utility, that information is also shown in the table.

Note that REPAIR SHRLEVEL CHANGE obtains an exclusive mass delete lock on a segmented (non-UTS) table space, which prevents execution of any application for which both of the following conditions are true:
  • The application is bound with ISO(UR).
  • The application issues a statement (such as a SELECT) that acquires a mass delete lock on that table space.

The following table shows which utilities can run concurrently with REPAIR LOCATE by KEY or RID.

Table 2. Utility compatibility with REPAIR, LOCATE by KEY or RID
Utility DUMP or VERIFY DELETE or REPLACE
CHECK DATA No No
CHECK INDEX Yes No
CHECK LOB Yes No
COPY INDEXSPACE Yes No
COPY TABLESPACE Yes No
DIAGNOSE Yes Yes
LOAD No No
MERGECOPY Yes Yes
MODIFY Yes Yes
QUIESCE Yes No
REBUILD INDEX No No
RECOVER INDEX 1 No No
RECOVER TABLESPACE No No
REORG INDEX 2 No No
REORG TABLESPACE UNLOAD CONTINUE or PAUSE No No
REORG TABLESPACE UNLOAD ONLY or EXTERNAL Yes No
REPAIR DELETE or REPLACE 3 No No
REPAIR DUMP or VERIFY Yes No
REPORT Yes Yes
RUNSTATS INDEX SHRLEVEL CHANGE Yes Yes
RUNSTATS INDEX SHRLEVEL REFERENCE Yes No
RUNSTATS TABLESPACE Yes No
STOSPACE Yes Yes
UNLOAD Yes No
Notes:
  1. REORG INDEX is compatible with LOCATE by RID, DUMP, VERIFY, or REPLACE.
  2. RECOVER INDEX is compatible with LOCATE by RID, DUMP, or VERIFY.
  3. REPAIR LOCATE INDEX PAGE REPLACE is compatible with LOCATE by RID or REPLACE.

The following table shows which utilities can run concurrently with REPAIR LOCATE by PAGE.

Table 3. Utility compatibility with REPAIR, LOCATE by PAGE
Utility or action TABLESPACE DUMP or VERIFY TABLESPACE REPLACE INDEX DUMP or VERIFY INDEX REPLACE
SQL read Yes No Yes No
SQL write No No No No
CHECK DATA No No No No
CHECK INDEX Yes No Yes No
CHECK LOB Yes No Yes No
COPY INDEXSPACE Yes Yes Yes No
COPY TABLESPACE Yes No Yes No
DIAGNOSE Yes Yes Yes Yes
LOAD No No No No
MERGECOPY Yes Yes Yes Yes
MODIFY Yes Yes Yes Yes
QUIESCE Yes No Yes No
REBUILD INDEX Yes No No N/A
RECOVER INDEX Yes No No No
RECOVER TABLESPACE (with no option) No No Yes Yes
RECOVER TABLESPACE ERROR RANGE No No Yes Yes
RECOVER TABLESPACE TOCOPY or TORBA No No No No
REORG INDEX Yes Yes No No
REORG TABLESPACE UNLOAD CONTINUE or PAUSE No No No No
REORG TABLESPACE UNLOAD ONLY or EXTERNAL Yes No Yes Yes
REPAIR DELETE or REPLACE No No No No
REPAIR DUMP or VERIFY1 Yes No Yes No
REPORT Yes Yes Yes Yes
RUNSTATS INDEX Yes Yes Yes No
RUNSTATS TABLESPACE Yes No Yes Yes
STOSPACE Yes Yes Yes Yes
UNLOAD Yes No Yes Yes
Note:
  1. REPAIR LOCATE INDEX PAGE REPLACE is compatible with LOCATE TABLESPACE PAGE.