Resetting restricted status after running the LOAD utility

The LOAD utility can place a table space or an index space into a restricted status. Several types of restricted status are possible.

Before you begin

You can issue the following command to discover which spaces are in a restricted status: 
-DISPLAY DATABASE (*) SPACENAM (*) RESTRICT

About this task

Your use of a table space in restricted status is severely limited. In general, you cannot access the data through SQL. You can only drop the table space or one of its tables, or perform some operation that resets the status.

  • Resetting COPY-pending status
    If you load with LOG NO and do not take an inline copy, LOAD places a table space in the COPY-pending status. Immediately after that operation, DB2 cannot recover the table space (although you can, by loading it again).
  • Resetting REBUILD-pending status
    LOAD sets index spaces to REBUILD-pending status when a REBUILD job ends before the INDEXVAL phase is complete.
  • CHECK-pending status after running LOAD
    The LOAD utility places a table space in CHECK-pending (CHKP) status if its referential integrity is in doubt or its check constraints are violated.
Parent topic: After running LOAD
Related reference:
Advisory or restrictive states
-DISPLAY DATABASE (DB2)