Concurrency and compatibility for QUIESCE

The QUIESCE 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 QUIESCE operations.
Target WRITE YES WRITE NO
Table space or partition DW/UTRO DW/UTRO
Partitioning index, data-partitioned secondary index, or partition DW/UTRO  
Nonpartitioned secondary index DW/UTRO  
Legend:
  • DW - Drain the write claim class - concurrent access for SQL readers
  • UTRO - Utility restrictive state - read-only access allowed

Compatibility

The following table shows which utilities can run concurrently with QUIESCE 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. QUIESCE does not set a utility restrictive state if the target object is DSNDB01.SYSUTILX.

Table 2. Compatibility of QUIESCE with other utilities
Action Compatible with QUIESCE?
CHECK DATA DELETE NO Yes
CHECK DATA DELETE YES No
CHECK INDEX Yes
CHECK LOB Yes
COPY INDEXSPACE SHRLEVEL CHANGE No
COPY INDEXSPACE SHRLEVEL REFERENCE Yes
COPY TABLESPACE SHRLEVEL CHANGE No
COPY TABLESPACE SHRLEVEL REFERENCE Yes
DIAGNOSE Yes
LOAD No
MERGECOPY Yes
MODIFY Yes
QUIESCE Yes
REBUILD INDEX No
RECOVER INDEX No
RECOVER TABLESPACE No
REORG INDEX No
REORG TABLESPACE UNLOAD CONTINUE or PAUSE No
REORG TABLESPACE UNLOAD ONLY or EXTERNAL Yes
REPAIR DELETE or REPLACE No
REPAIR DUMP or VERIFY Yes
REPORT Yes
RUNSTATS Yes
STOSPACE Yes
UNLOAD Yes

To run the QUIESCE utility on DSNDB01.SYSUTILX, ensure that QUIESCE is the only utility in the job step.

QUIESCE on SYSUTILX is an exclusive job; such a job can interrupt another job between job steps, possibly causing the interrupted job to time out.