Introduction to Oracle database 21c licensing
In the ever-evolving world of database technology, Oracle continues to introduce new features and enhancements to improve its database systems’ performance, security, and scalability.
With the release of Oracle Database 21c, several new features have been introduced that not only enhance the capabilities of the database but also require additional licensing. This informative article aims to help you understand which new features trigger additional licensing requirements.
New Features in Oracle Database 21c
Oracle Database 21c has introduced a plethora of new features. However, it’s important to note that some of these features are part of additional licensable options and may require extra costs.
Here are some of the critical features that fall into this category:
Oracle Real Application Clusters (RAC)
Oracle RAC has a new AutoUpgrade feature, which automates all the steps needed to upgrade an Oracle RAC database. This feature is part of Oracle Database 21c and requires additional licensing.
Oracle Multitenant
Oracle Multitenant has introduced several new features in Oracle Database 21c, including:
- AutoUpgrade for Non-CDB to PDB: This feature automates converting a database from a non-CDB to a PDB as part of a database upgrade.
- AutoUpgrade for PDB via Unplug-Plug-Upgrade: This feature automates unplugging a PDB from a CDB, plugging it into a higher version CDB, and upgrading the PDB to that new target version.
- DRCP Enhancements: You can now configure Database Resident Connection Pooling (DRCP) from the CDB to individual PDBs for improved PDB tenancy management.
Oracle Active Data Guard
Oracle Active Data Guard has a new feature called Standby Result Cache. This feature utilizes the result cache in an Active Data Guard standby database to cache the results of queries run on the physical standby database.
Oracle Database Vault
Oracle Database Vault has introduced two new features:
- ADMINISTER KEY MANAGEMENT Statement Protection: With Oracle Database Vault command rules, you can now protect the ADMINISTER KEY MANAGEMENT statement.
- Prevention of Local Oracle Database Vault Policies: A DV_OWNER common user in the CDB root can now prevent local users from creating Oracle Database Vault controls on common objects in a pluggable database (PDB).
Frequently Asked Questions
Do all new features in Oracle Database 21c require additional licensing?
No, not all new features require additional licensing. Only certain features that are part of additional licensable options require extra costs. This article only highlights which new features are not part of the database license.
How can I find out if a feature requires additional licensing?
Oracle’s official documentation provides information about the licensing requirements of each feature. You can also contact Oracle or a licensing expert for more detailed information.
What happens if I use a feature that requires additional licensing without realizing it?
Using a feature that requires additional licensing without the appropriate license could lead to compliance issues. Verifying the licensing requirements before using a new feature is always best.
Need Help with Database Licensing?
Understanding Oracle’s licensing policies can be complex, especially regarding new features and enhancements. If you need assistance with Oracle database licensing, don’t hesitate to contact Redress Compliance.
Our team of experts is ready to help you navigate the complexities of Oracle licensing and ensure that you fully comply with all requirements. Contact us today for more information.
