DB2 Purescale Members Test
In DB2 pureScale, a member refers to an individual DB2 database server instance within the pureScale cluster. These members work together to process database requests in a shared-disk, shared-data architecture, coordinated by the Cluster Caching Facility (CF).
Roles and Responsibilities
Query Processing: Members handle client connections and execute queries.
Buffer Pool Management: Each member maintains its own buffer pool.
Coordination with CF: Members interact with the CF for locking, page ownership, and consistency.
Workload Distribution: DB2 can route queries to different members for load balancing.
This test monitors DB2 pureScale Members and reports the metrics like - Uptime, Is member running?, Has been restarted? etc.
Target of the test : A DB2 Purescale database cluster.
Agent deploying the test : An internal agent
Outputs of the test : One set of results for the target DB2 Purescale cluster being monitored
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
Specify the IP address of the DB2 server in this text box. |
|
Port |
Specify the port at which the target host is listening. The default port is 50000. |
|
Username, Password |
To monitor Db2 UDB database server, the eG agent should be configured with the credentials of a user with any of the following privileges SYSADM or SYSCTRL or SYSMAINT or SYSMON. Specify the credentials of such a user in the User and Password text boxes. Confirm the Password by retyping it in the Confirm Password text box. |
|
Database |
The test uses a database on the monitored Db2 Purescale. Specify the name of the database in the Database text box. |
|
SSL |
If the target database server monitored is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No. |
|
Include Available Nodes |
In the Include Available Nodes text box, provide a comma-separated list of all the available nodes to be included for monitoring. This way, the test monitor and collect metrics from all the available nodes in the cluster. By default, this parameter is set to none. The format of this configuration is: HOSTNAME:PORT, for example, 172.16.8.136:3306,172.16.8.139:3306 |
|
Confirm Password |
Confirm the Password by retyping it in the Confirm Password text box. |
|
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
State |
Indicates the current state of member server in the cluster. |
|
The States reported by this measure and their corresponding numeric equivalents are described in the table below:
Note: By default, this measure reports the above-mentioned States while indicating the status of member server. However, in the graph of this measure, states will be represented using their corresponding numeric equivalents only. |
||||||||||||||
|
Is member running? |
Indicates if the member server is still running. |
|
The States reported by this measure and their corresponding numeric equivalents are described in the table below:
Note: By default, this measure reports the above-mentioned States while indicating the running status of member server. However, in the graph of this measure, states will be represented using their corresponding numeric equivalents only. |
||||||||||||||
|
Uptime |
Indicates the time for which the server has been up since last restart. |
Minutes |
|
||||||||||||||
|
Uptime since last measure |
Indicates the time for which the server has been up since the last measurement, |
Minutes |
|
||||||||||||||
|
Has been restarted? |
Indicates if the sever has been restarted since the last measurement period. |
|
The States reported by this measure and their corresponding numeric equivalents are described in the table below:
Note: By default, this measure reports the above-mentioned States while indicating if the server has been restarted. However, in the graph of this measure, states will be represented using their corresponding numeric equivalents only. |
||||||||||||||
|
Is under maintenance? |
Indicates if the server is under maintenance. |
|
The States reported by this measure and their corresponding numeric equivalents are described in the table below:
Note: By default, this measure reports the above-mentioned States while indicating if server is under maintenance. However, in the graph of this measure, states will be represented using their corresponding numeric equivalents only. |