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.

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 RECOVER operations.
Target RECOVER (no option) RECOVER TOCOPY, TORBA, or TOLOGPOINT RECOVER PART TOCOPY, TORBA, or TOLOGPOINT RECOVER ERROR-RANGE Redirected recovery- source objects Redirected recovery-target objects
Table space or partition DA/UTUT DA/UTUT DA/UTUT DA/UTUT CW/UTRW1 none/UTRW DA/UTUT
Partitioning index, data-partitioned secondary index, or physical partition2 DA/UTUT DA/UTUT DA/UTUT DA/UTUT CW/UTRW1 NA NA
Nonpartitioned secondary index3 DA/UTUT DA/UTUT DA/UTUT DA/UTUT CW/UTRW1 NA NA
RI dependents none CHKP (YES) CHKP (YES) none none CHKP (YES)
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.
Note: Start of changeRECOVER does not set a utility restrictive state if the target object is one of the following table spaces:
  • DSNDB01.SYSUTILX
  • Start of changeFL 509DSNDB01.SYSTSUTMEnd of change
  • Start of changeFL 509DSNDB01.SYSTSUTXEnd of change
End of change

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. For redirected recovery, the information in this table pertains to the target object.

Table 2. Compatibility of RECOVER with other utilities
Action Compatible with RECOVER (no option)? Compatible with RECOVER TOCOPY, TORBA, or TOLOGPOINT? 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
COPYTOCOPY Yes Yes Yes
DIAGNOSE Yes Yes Yes
LOAD No No No
MERGECOPY Yes Yes Yes
MODIFY RECOVERY Yes Yes Yes
MODIFY STATISTICS No No No
QUIESCE No No No
REBUILD INDEX No No No
REORG INDEX2 Yes No Yes
REORG TABLESPACE1 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
Notes for redirected recovery:

All utilities are compatible on the source object when redirected recovery from a source object is running, with the following exceptions:

  1. Redirected recovery from a source object is compatible with REORG TABLESPACE of the source object except for the following REORG operations:
    • REORG TABLESPACE SHRLEVEL CHANGE or REFERENCE operations that materialize pending ALTER operations. In the case of indexes, a redirected recovery from a source index is not compatible with a REORG TABLESPACE operation that materializes pending ALTER operations on the underlying source table space.
    • REORG TABLESPACE with the REBALANCE option on a partition-by-range (PBR) table space
    • REORG TABLESPACE on a partition-by-growth (PBG) table space when all of the following situations are true:
      • DROP_PART YES is specified or DROP_PART NO is specified while the REORG_DROP_PBG_PARTS subsystem parameter is set to ENABLE.
      • The table space has a MAXPARTITIONS value that is greater than one.
      • FASTSWITCH YES is specified.
      • The table is not defined with DATA CAPTURE CHANGES.
  2. Redirected recovery from a source object is compatible with REORG INDEX of the source object except for REORG INDEX SHRLEVEL CHANGE or REFERENCE jobs that materialize pending ALTER operations.

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. For more information about running RECOVER on a catalog or directory table space, see Recovering catalog and directory objects.