Oracle database 20c software hasn’t released yet. But it has some really interesting new features. I shall be listing by product category them, some in this post and few in the subsequent posts followed by the explanation. Since in this week, I am teaching High Availability New Features anyways, so here is the list of the new features of clusterware and rac.
Clusterware New Features
Common Data Model Across Fleet Patching and Provisioning Servers
The common data model across Fleet Patching and Provisioning (FPP) servers provides a unified view of fleet targets regardless of the FPP server deployment.
The unified view of the common model provides an easier and simplified operation of large estates and cloud management across multiple data centers.
Clusterware REST API
The Clusterware REST APIs enable customers to remotely execute commands on their cluster and to monitor the execution, including output, error codes and time to execute. Support is provided for existing Oracle Clusterware command line interfaces.
REST API-based management based on well-known Oracle Clusterware command line interfaces simplifies cluster management in the Oracle Cloud, at remote physical locations or locally provisioned.
Pluggable Database Cluster Resources
Pluggable Database (PDB) Cluster Resources enables direct mapping and control of those PDB resources. Unlike in previous versions, in which cluster resources for Multitenant databases were mapped against the Container Database (CDB) using a control of Pluggable Databases (PDBs) using services.
Pluggable Database (PDB) Cluster Resources enable a tighter and more effective control of PDBs in an Oracle RAC Database.
RAC New Features
Cache Fusion Hardening
The Global Cache Service (LMS) process is vital to the operation of an Oracle Real Application Clusters (Oracle RAC) Database. Cache Fusion Hardening helps to ensure that the critical LMS process remains running despite some discrepancies between instances that would otherwise lead to a LMS and consequently database instance failures.
Cache Fusion Hardening increases availability by reducing outages, particularly in consolidated environments in which multiple Pluggable Databases (PDBs) are operated in the same Oracle RAC Container Database.
Deploying Grid Infrastructure Management Repository (GIMR) into a Separate Oracle Home
Starting with Oracle Grid Infrastructure 20c, you must configure the Grid Infrastructure Management Repository (GIMR) in a separate Oracle home, instead of in the Grid home. This option is available when you configure GIMR during a fresh Oracle Grid Infrastructure installation or you add a GIMR to an existing deployment.
A separate Oracle home for the GIMR ensures faster rolling upgrades, less errors, and fewer rollback situations. The Oracle Grid Infrastructure installation owner user must own the GIMR home.
Remote GIMR Support for Oracle Standalone Clusters
The remote Grid Infrastructure Management Repository (GIMR) feature for Oracle Standalone Cluster enables you to use a centralized GIMR. This feature does not require local cluster resources to host the GIMR.
The remote GIMR feature provides access to a persistent data store that significantly enhances the proactive diagnostic functionality of Cluster Health Monitor, Cluster Health Advisor, and Autonomous Health Framework clients. The remote GIMR feature saves cost by freeing up local resources and licensed database server resources.
In the next post, I shall list the Automatic Storage Management(ASM) new features.
Hope that helps.