Concurrency and compatibility for RECOVER

The RECOVER 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. However, if a nonpartitioned secondary index exists on a partitioned table space, utilities that operate on different partitions of a table space can be incompatible because of contention on the nonpartitioned secondary index.

The following table shows which claim classes RECOVER claims and drains and any restrictive state that the utility sets on the target object.

Claims

Table 1. Claim classes of RECOVER operations.
Target RECOVER (no option) RECOVER TORBA or TOCOPY RECOVER PART TORBA or TOCOPY RECOVER ERROR-RANGE
Table space or partition DA/UTUT DA/UTUT DA/UTUT DA/UTUT CW/UTRW1
Partitioning index, data-partitioned secondary index, or physical partition2 DA/UTUT DA/UTUT DA/UTUT DA/UTUT CW/UTRW1
Nonpartitioned secondary index3 DA/UTUT DA/UTUT DA/UTUT DA/UTUT CW/UTRW1
RI dependents none CHKP (YES) CHKP (YES) none
Legend:
  • CHKP (YES): Concurrently running applications enter CHECK-pending after commit
  • CW: Claim the write claim class
  • DA: Drain all claim classes, no concurrent SQL access
  • DR: Drain the repeatable read class, no concurrent access for SQL repeatable readers
  • RI: Referential integrity
  • UTRW: Utility restrictive state, read-write access allowed
  • UTUT: Utility restrictive state, exclusive control
  • none: Object is not affected by this utility
Note:
  1. During the UTILINIT phase, the claim and restrictive states change from DA/UTUT to CW/UTRW.
  2. Includes document ID indexes and node ID indexes over nonpartitioned XML table spaces and XML indexes.
  3. Includes document ID indexes and node ID indexes over partitioned XML table spaces.

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

Compatibility

The following table shows which utilities can run concurrently with RECOVER 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 documented in the table.

Table 2. Compatibility of RECOVER with other utilities
Action Compatible with RECOVER (no option)? Compatible with RECOVER TOCOPY or TORBA? Compatible with RECOVER ERROR-RANGE?
CHECK DATA No No No
CHECK INDEX No No No
CHECK LOB No No No
COPY INDEXSPACE No No No
COPY TABLESPACE No No No
DIAGNOSE Yes Yes Yes
COPYTOCOPY No No No
LOAD No No No
MERGECOPY No No No
MODIFY RECOVERY No No No
MODIFY STATISTICS No No No
QUIESCE No No No
REBUILD INDEX No No No
REORG INDEX Yes No Yes
REORG TABLESPACE No No No
REPAIR LOCATE INDEX Yes No Yes
REPAIR LOCATE TABLESPACE No No No
REPORT Yes Yes Yes
RUNSTATS INDEX No No No
RUNSTATS TABLESPACE No No No
STOSPACE Yes Yes Yes
UNLOAD No No No

To run on DSNDB01.SYSUTILX, RECOVER must be the only utility in the job step and the only utility running in the Db2 subsystem.

RECOVER on any catalog or directory table space is an exclusive job; such a job can interrupt another job between job steps, possibly causing the interrupted job to time out.