Status monitoring of a Db2 pureScale instance
- Are the hosts that comprise a Db2 pureScale instance active or not?
- Which hosts are functioning as cluster caching facilities or member servers?
- Are there hosts that are functioning as both a member and a cluster caching facility?
- Are there hosts that are running more than one member?
- Is a member running on its preferred home host?
- For configurations with two cluster caching facilities, which one is functioning as the primary server? What is the current state of the secondary cluster caching facility: PEER or CATCHUP?
- What is the current state of the members that comprise an instance? For example, has any member been stopped using the db2stop command? Or is any member currently waiting to fail back to its home host?
- Do any cluster caching facility or member servers indicate an active alert that requires investigation?
Included in the information returned by many of these interfaces is state and alert information. The state of a host, a member or a cluster caching facility reflects the current operational capacity of the object in question. For example, a member can be STARTED, STOPPED, RESTARTING, WAITING_FOR_FAILBACK, ERROR or UNKNOWN.
Alerts are used to indicate that there is something that requires further investigation. If an alert is raised for one or more cluster caching facilities or members in an instance, problems might exist that require investigation.