DSNB313I csect-name GROUP BUFFER POOL gpbname TO BE DISCONNECTED REASON=reason LOSSCONN PERCENTAGE=percentage
Explanation
This Db2 member is disconnecting from group buffer pool gpbname because it has lost connectivity to the coupling facility in which the group buffer pool is allocated.
- NOSFMPOL
- MVS cannot determine the scope of the loss of connectivity because there is no active SFM policy with CONNFAIL(YES).
- LOSSCONN
- MVS determined that the scope of the loss of connectivity was less than 100%.
- NOXESEVL
- MVS started to try to determine the scope of the loss of connectivity, but some condition occurred which prevented MVS from being able to complete the evaluation. One example of such a condition would be that the SFM policy became inactive while MVS was trying to do the evaluation.
If reason is LOSSCONN, then percentage indicates the percentage of lost connectivity that was calculated by MVS. MVS evaluates the scope of the loss of connectivity in terms of SFM weights associated with the systems which have lost connectivity and which have active connectors to the coupling facility structure (if there are systems that do not have an active connector to the coupling facility structure, then those systems are not factored into the "percentage loss of connectivity" calculation).
If reason is not LOSSCONN, then percentage is not applicable (it should appear as zero).
System action
The Db2 member disconnects the group buffer pool, putting its connection into a "failed-persistent" 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).
System programmer response
Use the START DATABASE command to recover the LPL pages. If DSNDB01 or DSNDB06 objects have LPL pages, you might need to recover these first, before proceeding with LPL recovery for other objects.