Oracle 19c brings a host of new features and enhancements to Real Application Cluster (RAC), significantly improving resource management, cluster flexibility, and overall performance. Here’s a breakdown of the key updates:
- OCR and Voting Files on Shared File Systems
Reintroducing flexibility, Oracle 19c (19.3) allows standalone clusters to place Oracle Cluster Registry (OCR) and Voting Disk files on shared file systems. This was previously unsupported in Oracle Grid Infrastructure 12c Release 2 (12.2). However, for Oracle Domain Services Clusters, these files must still reside in quorum failure groups managed by ASM.
- Dynamic Resource Runtime Management
With Oracle RAC 19.3, the RAC Resource Runtime Management feature has been introduced. This feature allows automatic, real-time adjustments to resource allocations, moving beyond the static allocation that only occurred during database startup in previous versions.
- Service Failback to Preferred Instance
Oracle 19c enhances service management by allowing dynamic database services, placed using preferred and available settings, to automatically revert to the preferred instance once it becomes available after a failover to an alternative instance.
- Colocation Tags for Connection Routing
Oracle 19c introduces the colocation_tag in connect strings. This feature enables clients with the same colocation tag to be routed to the same instance offering a particular service, if possible. If colocation is not feasible when a connection is initiated, the tag is ignored, and connections are routed to any available instance as usual.
- Optional Grid Infrastructure Management Repository (GIMR)
Starting with Oracle Grid Infrastructure 19c, the Grid Infrastructure Management Repository (GIMR) is optional for new installations of Oracle Standalone Clusters. However, it remains a mandatory component for Oracle Domain Services Clusters. The GIMR, or Management Database (MGMTDB), stores real-time performance data, fault diagnostics, cluster-wide events, and metadata required for fleet patching and provisioning.
- Deprecation of Addnode Script
The addnode script, previously used for adding nodes to a cluster, has been deprecated starting with Oracle 19c. This change streamlines cluster management, encouraging the use of modern, integrated tools.
- Deprecation of Third-Party Clusterware Integration
From Oracle Clusterware 19c (19.5) onwards, the integration of vendor or third-party clusterware with Oracle Clusterware is no longer supported. This move emphasizes Oracle’s commitment to a cohesive, unified cluster management ecosystem.
Oracle 19c's Real Application Cluster advancements reflect a focus on flexibility, ease of management, and enhanced resource utilization, ensuring that organizations can run their mission-critical applications with greater efficiency and reliability
No comments:
Post a Comment