Monitoring DB2 pureScale environments
Despite the fact that DB2 pureScale addresses high availability, we should know, at any moment, the status of the components of our system. Here we can enumerate the state of members, the current state of caching facilities, any alerts generated by cluster facilities, and performance information regarding locking mechanisms and buffer pools.
In the following recipe, we will cover the monitoring tasks and explain some monitoring elements related to DB2 pureScale components.
Getting ready
There are plenty of methods for monitoring our system, such as administrative views, table functions, clp, and shell commands.
Members and caching facilities can be in different states of functionality. Members can be in the following states:
|
Member state |
Description |
|---|---|
|
|
Member is up and ready to accept connections. |
|
|
Member has been stopped manually. |
|
|
Member is restarting; a member can also have this state if restarting light (When a member... |
