Initiating member crash recovery
Member crash recovery is almost always performed automatically, with no user action required. You will only initiate member crash recovery manually in situations where the cluster manager has repeatedly failed in its attempt to perform crash recovery, or it is not present (perhaps because cluster management was disabled), or when the autorestart configuration parameter is set to OFF.
About this task
If the Db2® pureScale® instance has more than one member requiring member crash recovery, the cluster manager issues multiple member crash recoveries in parallel. This helps avoid hang situations caused by one failed member having a dependency on resources held by another failed member.
Procedure
When the RESTART DATABASE command is issued, Db2 determines whether a group crash recovery or a member crash recovery is required.
Results
Once member crash recovery completes, the database on the given member will be activated and available to receive connections from other applications.