DSNI017I RESOURCE TYPE resource-type NAME resource-name IS INCONSISTENT DUE TO ONE OR MORE PENDING STATES

Explanation

There are two possible reasons for this message:
  1. The header page of a table space, index, or partition belonging to a database defined as ROSHARE OWNER could not be marked as consistent during the processing of the STOP DATABASE command because one or more of the following was true:
    • The table space, index, or partition is in recovery pending status.
    • The table space, index, or partition is in check pending status.
    • The table space, index, or partition has pages in the logical page list (LPL).
    • The table space, index, or partition status has a utility in progress (UTUT status on the output from a DISPLAY DATABASE command).
    • The table space, index, or partition has a utility in progress that allows read-only access (UTRO on the output from a DISPLAY DATABASE command).
    • An I/O error range exists.
  2. A retained lock is held on the table space, index, or partition. The retained lock could be signifying a pending status.
If the STOP DATABASE command was issued without specifying the SPACENAM parameter, then one or more of the conditions stated above is true for one or more table spaces, indexes, or partitions in the specified database.
resource-type and resource-name
The type and name of the resource that the message identifies. For an explanation of resource-type and resource-name values, see Resource types.

System action

For case 1, if the STOP DATABASE command was specified with the SPACENAM parameter, the table space, index, or partition is stopped. Db2 does not allow access to an inconsistent table space, index, or partition by any ROSHARE READ system.

For case 2, no access to an inconsistent table space, index, or partition is allowed until the retained lock is released by the failed system at completion of its restart.

User response

Issue a DISPLAY DATABASE command to display the status of the object in question. Resolve the pending states and then reissue the STOP DATABASE command to ensure that the consistency indicator is reset.

Severity

4 (warning)