Node 1: state NOT ="PEER" and member_type="CF"
Node 2: most_recent_state="PRIMARY" and member_type="CF"
This should cause the rule to fire.
This rule checks if one node is in a PRIMARY state and another is PEER state. This applied to clusters.
The backup CF is ready to take over the responsibilities of the primary CF in the event of a primary CF failure.
In DB2 Purescale, at least one CF should be active and the best practice is to have another CF for backup. All of the other settings (STOPPED, RESTARTING, ERROR, etc.) are all states where the backup will not take over.
NOTE: CF is Cluster Caching Facility used to coordinate locking through a global lock manager to prevent conflicting access to the same table data by different members, i.e. this is used in the rule to indicate that the monitored environment is a Cluster.
A Backup CF can be in the following states:
If CF is in Error state, DB2 Cluster services will not attempt to restart the CF unless the alert has been cleared. Look at the alert data present for this CF and act accordingly.
Troubleshooting recommendations
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center