Coupling facility recovery scenarios

Looking at a few problem scenarios might help if you need to recover a coupling facility.

Problem: loss of coupling facility (CF)
You might encounter a failure that is treated by z/OS® and Db2 as a total loss of connectivity to the coupling facility and coupling facility structures.
Problem: a subset of members have lost connectivity (non-duplexed)
In a data sharing environment with simplexed structures, one or more members might lose connectivity to the coupling facility, while other members do not. This might happen if a link is detached between a system and the coupling facility.
Problem: a subset of members have lost connectivity (duplexed)
In a data sharing environment with duplexed structures, one or more members might lose connectivity to the coupling facility, while other members do not. This problem might happen if a link is detached between a system and the coupling facility.
Problem: allocation failure of the group buffer pool
One problem that you might encounter is an allocation failure of the group buffer pool.
Problem: storage shortage in the group buffer pool
In a data sharing environment, you might encounter a problem that is caused by a storage shortage in the group buffer pool.
Problem: storage shortage in the SCA
In a data sharing environment, you might encounter a problem that is caused by a storage shortage in the SCA.
Problem: storage shortage in the lock structure
In a data sharing environment, you might encounter a problem that is caused by a storage shortage in the lock structure.
Deallocating structures by force
In a few exceptional cases, you might need to deallocate a structure by force to get Db2 restarted.

Parent topic: How Db2 recovers from coupling facility failures