DSNB209I   csect-name-BUFFER MANAGER TABLESPACE/INDEXSPACE CLEAN-UP ROUTINE (DSNB1CFC) HAS BEEN SCHEDULED FOR DBNAME = database-name, SPACENAME = space-name , INSTANCEinstance-number , PSID = X'psid'

Explanation

DB2® detected an abnormal condition for one of the following reasons:

  • The associated table space or index space contains modified pages that cannot be written to DASD for a period of time that is longer than expected. This situation can be caused by either an unusually long period of continuous updates or by an internal logic error.
  • An abnormal termination occurred because of inconsistent data or an incomplete update to the page.

DB2 scheduled the table space or index space cleanup routine (DSNB1CFC) for the associated table space or index space. DSNB1CFC acquires a drain lock to ensure that no updates are in progress. Data is inaccessible to users during the cleanup process.

For recoverable inconsistent pages with unbalanced write intents, DB2 initiates the recovery process and reconstructs the pages using the DB2 log. For other modified pages with unbalanced write intents, the buffer manager forces the pages to be written back to DASD and then makes the buffer space available for reassignment.

csect-name
The name of the control section that issued the message.
database-name
The name of the database that is associated with the action.
space-name
The name of the table space or index space that is associated with the action.
instance-number
The instance number of the table space or index space.
psid
The internal identifier for the table space or index space. This value is used to associate this message with the follow-on message DSNB221I, which might be issued.

System action

DB2 is ready to clean up the associated table space or index space. However, before any cleanup is initiated, DB2 requests a drain on the table space or index space. DB2 waits indefinitely for this drain. Therefore, all activities against the table space or index space, or both, must be quiesced before the cleanup process can proceed. After the cleanup process completes, the table space or index space is automatically made accessible to users.

User response

If the cleanup activity does not seem to finish,DB2 might still be waiting for a drain on the table space or index space. Issue a -DISPLAY DATABASE CLAIMERS command for the table space or index space in question to determine whether the cleanup routine is still waiting for a drain. If it is still waiting, identify the claimers of the table space or index space. If the jobs are holding claims for a very long duration (for example, they are waiting for input), you might need to cancel those jobs in order to allow the cleanup process to proceed.