DSNB314I csect-name DAMAGE ASSESSMENT TO BE TRIGGERED FOR GROUP BUFFER POOL gpbname REASON=reason
Explanation
Db2 is about to initiate the damage assessment function for group buffer pool gpbname because of a detected error in either the coupling facility in which the group buffer pool was allocated, or in the connectivity from the MVS systems to the coupling facility.
- 100%LCON
- An error has occurred in a coupling facility or in the attachments of MVS systems to a coupling facility which has caused all Db2 members to lose connectivity to the named group buffer pool.
- STRFAIL
- There was an error in the coupling facility in which the group buffer pool was allocated which caused a failure of the coupling facility structure.
- CONERROR
- The named group buffer pool is currently allocated in a coupling facility, but Db2 cannot connect to the group buffer pool because the system on which it is running does not currently have connectivity, and MVS has indicated that currently no other member is actively connected and has connectivity.
- DAP
- The named group buffer pool is in damage assessment pending (DAP) state.
System action
Db2 triggers the damage assessment function to ensure that any changed pages that might have been cached in the affected group buffer pool get marked as "needing recovery" (the objects to which the pages belong are marked in GRECP state). This message should be immediately followed by a DSNB304I message indicating that the group buffer pool has been entered into damage assessment pending (DAP) state.
If there are transactions that are in progress at the time of the connectivity failure, Db2 might need to add pages to the logical page list (LPL).
There is one case where Db2 triggers damage assessment for a group buffer pool, but no DSNB314I message is issued. This case is where the group buffer pool was manually deleted (via MVS SETXCF FORCE commands) while all connections to the group buffer pool were failed-persistent (e.g. all Db2 members were down). In this case, the next Db2 member to connect to the group buffer pool will cause MVS to try to reallocate a new instance of the group buffer pool in some coupling facility in the CFRM policy preference list. If the allocation succeeds, then Db2, by doing a coupling facility structure version id comparison, will detect that the previous instance of the group buffer pool had been lost, and will trigger damage assessment. But you will not receive the DSNB314I message in this case, nor will you receive the DSNB304I or DSNB305I messages indicating that the group buffer pool has been put into damage assessment pending (DAP) state. You will only receive a series of DSNB322I and/or DSNB323I messages indicating those pagesets or partitions that have been put into GRECP state by the damage assessment process.
System programmer response
Use the START DATABASE command to recover the LPL pages and GRECP objects. If DSNDB01 or DSNDB06 objects are in GRECP state or have LPL pages, you might need to recover these first, before proceeding with GRECP or LPL recovery for other objects.