Concurrency and compatibility for LOAD

Depending on the specified LOAD utility options and the target object, certain processes and utilities can run at the same time as LOAD.

Claims and drains

The following table shows the claim classes that LOAD drains and the restrictive states the utility sets.

Table 1. Claim classes of LOAD operations
Target LOAD SHRLEVEL NONE LOAD PART SHRLEVEL NONE LOAD SHRLEVEL CHANGE LOAD PART SHRLEVEL CHANGE
Table space, index, or physical partition of a table space or index space DA/UTUT DA/UTUT CW/UTRW CW/UTRW
Nonpartitioned secondary index1 DA/UTUT DR CW/UTRW CW/UTRW
Data-partitioned secondary index2 DA/UTUT DA/UTUT CW/UTRW CW/UTRW
Index logical partition3 None DA/UTUT None CW/UTRW
Primary index (with ENFORCE option only) DW/UTRO DW/UTRO CR/UTRW CR/UTRW
RI dependents CHKP (NO) CHKP (NO) CHKP (NO) CHKP (NO)
Legend:
  • CHKP (NO): Concurrently running applications do not see CHECK-pending status after commit.
  • CR: Claim the read claim class.
  • 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.
  • 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.
  • UTRW: Utility restrictive state, read/write access allowed.
  • None: Object is not affected by this utility.
Note:
  1. Includes the document ID indexes and node ID indexes over non-partitioned XML table spaces and XML indexes.
  2. Includes document ID indexes and node ID indexes over partitioned XML table spaces.
  3. Includes logical partitions of an XML index over partitioned table spaces.
  4. For nonpartitioned secondary indexes, LOAD PART drains only the logical partition.

Compatibility

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.

The following table shows whether other utilities are compatible with LOAD and can run concurrently 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.

Table 2. Compatibility of LOAD with other utilities
Action LOAD SHRLEVEL NONE LOAD SHRLEVEL CHANGE
BACKUP SYSTEM Yes Yes
CHECK DATA DELETE NO No No
CHECK DATA DELETE YES No No
CHECK INDEX No No
CHECK LOB No No
COPY INDEXSPACE SHRLEVEL CHANGE No Yes
COPY INDEXSPACE SHRLEVEL REFERENCE No No
COPY TABLESPACE SHRLEVEL CHANGE No Yes
COPY TABLESPACE SHRLEVEL REFERENCE No No
COPYTOCOPY No Yes
DIAGNOSE Yes Yes
LOAD SHRLEVEL CHANGE No Yes
LOAD SHRLEVEL NONE No No
MERGECOPY No Yes
MODIFY RECOVERY No Yes
MODIFY STATISTICS No Yes
QUIESCE No No
REBUILD INDEX No No
RECOVER (no options) No No
RECOVER ERROR RANGE No No
RECOVER TOCOPY or TORBA No No
REORG INDEX No No
REORG TABLESPACE UNLOAD CONTINUE or PAUSE No No
REORG TABLESPACE UNLOAD ONLY or EXTERNAL No No
REPAIR DUMP or VERIFY No No
REPAIR LOCATE KEY or RID DELETE or REPLACE No No
REPAIR LOCATE TABLESPACE PAGE REPLACE No No
REPORT Yes No
RESTORE SYSTEM No No
RUNSTATS INDEX SHRLEVEL CHANGE No Yes
RUNSTATS INDEX SHRLEVEL REFERENCE No No
RUNSTATS TABLESPACE SHRLEVEL CHANGE No Yes
RUNSTATS TABLESPACE SHRLEVEL REFERENCE No No
STOSPACE Yes Yes
UNLOAD No Yes

SQL operations and other online utilities on the same target partition are incompatible.