DB2 Purescale Caching Facility Test
The DB2 pureScale Caching Facility (CF) is a central component of the DB2 pureScale architecture that ensures data consistency and coordination across multiple DB2 members (nodes) in a clustered environment.
The CF is a specialized server process that manages shared data page access, locking, and buffer pool coordination among all DB2 members. It acts as a traffic controller for data in memory, ensuring that all nodes have a consistent and up-to-date view of the database.
Monitoring the DB2 Purescale Caching Facility is crucial for ensuring Global Lock Management, Buffer Pool Coordination, Page Shipping and Recovery Support.
The DB2 Purescale Caching Facility Test continuously monitors the Caching Facility and reports the metrics like - Current group buffer pool size, Current shared communication area size, arget lock size, Configured memory size 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 |
|---|---|---|---|
|
Current group buffer pool size |
Indicates the current size of group bufferpool. |
MB |
Bufferpool size should be optimal so that requests are processed from it, as well as there should be space to add new items to cache on decent rate. |
|
Configured group buffer pool size |
Indicates the size of group bufferpool configured to use. |
MB |
Bufferpool size should be optimal so that requests are processed from it, as well as there should be space to add new items to cache on decent rate. |
|
Target group buffer pool size |
Indicates the current target for bufferpool usage. |
MB |
The target buffer size depends of the use case, if the data is quite varied, you may need to have a low target like 50% so that there is enough space for new items. |
|
Current lock size |
Indicates the current memory utilized by locks. |
MB |
|
|
Configured lock size |
Indicates the configured memory utilization for locks. |
MB |
|
|
Target lock size |
Indicates the target size of locks. |
MB |
|
|
Current shared communication area size |
Indicates the amount of memory allocated for shared communication area. |
MB |
|
|
Configured shared communication area size |
Indicates the amount of memory configured for allocation for shared communication area. |
MB |
|
|
Target shared communication area size |
Indicates the amount of memory targeted for allocation for shared communication area |
MB |
|
|
Current memory size |
Indicates the current size of memory size of caching facility. |
MB |
|
|
Configured memory size |
Indicates the configured size of memory size of caching facility. |
MB |
|
|
Current memory usage |
Indicates the amount of memory currently in use out of total memory configured. |
% |
|
