IBM Db2 pureScale Feature enhancements
Db2 version 11.5 continues to build on Db2 pureScale Feature support and provides several enhancements.
The following table displays a list of the new Db2
pureScale Feature
enhancements in 11.5:
| Enhancement | Description |
|---|---|
| Improved re-use of free pages across Db2 members | For tables that have the default APPEND OFF option set, re-use of free space on data pages has been improved. Particularly in the case where the majority of DELETE operations are performed on a distinct subset of members in the cluster. |
| Simplified Geographically dispersed Db2 pureScale cluster (GDPC) configuration | Simplified geographically dispersed Db2 pureScale cluster (GDPC) deployment by automating the configuration of public network equivalency resources for the CF and the condition response pair for the public ethernet IP subnet. This lowers the total cost of ownership in both initial GDPC setup as well as on-going maintenance. |
| Improved CF recovery time | On all Db2 pureScale configurations, CF recovery is faster in public Ethernet failure scenarios. |
| Cross Invalidation Connections in RDMA Networks | Multiple cross invalidation (XI) connections in RDMA networks can improve TPS performance in GDPC clusters. |
| IBM® Storage Scale changes to Db2 pureScale® instances | The default cipherList Security mode is changed to AUTHONLY from EMPTY. Some IBM Storage Scale configuration parameters have changed. workerThreads is used instead of worker1Threads, where the default value is configured to 512. maxFilesToCache default value has been changed to 15000. Lastly, the configuration automatic GPL compilation feature is enabled. |
| New registry variable supports enhanced security | Host-based firewall enablement is now an option for single-node, DPF, and pureScale Db2 configurations, through the use of the new DB2_FIREWALL_PORT_RANGE registry variable. |
| Improved castout performance | Reduced contention on the CF during page castout, improving overall performance. |
| Improved currently committed semantics | Currently committed semantics now apply to applications on any member. If a row reader is accessing a row that is being updated or deleted by an application on a remote member, the local member now retrieves the currently committed row data from the remote member. |