Oracle Multitenant option use cases
Summarize
Summary of Oracle Multitenant Option Use Cases
The Oracle Multitenant option enables efficient database management by allowing multiple pluggable databases (PDBs) within a single container database (CDB). Understanding its licensing requirements is essential for effective IT Asset Management and Software Asset Management.
Show less
Key Features
- Not in Use: If a database instance has fewer user-created PDBs than required, no additional licensing is needed.
- In Use: Instances exceeding the minimum user-created PDB requirement require additional licensing across all hosts in the cluster.
- Exceeds Maximum PDB Amount: If a database instance surpasses the maximum allowable PDBs, it is considered out of compliance, necessitating removal of excess PDBs to align with licensing rules.
Key Outcomes
By correctly applying the Oracle Multitenant option licensing, customers can ensure compliance and optimize their database resources. This understanding helps avoid potential licensing penalties and supports efficient management of database instances within ServiceNow's Software Asset Management framework.
You can view the following use cases to better understand licensing requirements for the Oracle Multitenant option.
The Oracle Multitenant option is not in use
In this scenario, Database Instance 1 and Database Instance 2 are running Oracle Database 12.1 Enterprise Edition and contain one user-created PDB each. Database Instance 3 is running Oracle Database 18c Enterprise Edition and also contains one user-created PDB. Since none of the database instances meet or exceed the minimum number of user-created PDBs for which the Oracle Multitenant option is required, the option is not in use on any of the database instances. Additional licensing for the Oracle Multitenant option is not required on any hosts within the cluster.
The Oracle Multitenant option is in use
In this scenario, Database Instance 1 and Database Instance 2 are running Oracle Database 12.1 Enterprise Edition. Database Instance 1 contains three user-created PDBs, while Database Instance 2 contains one user-created PDB. Database Instance 3 is running Oracle Database 18c Enterprise Edition and contains five user-created PDBs. Since both Database Instance 1 and Database Instance 3 exceed the minimum number of user-created PDBs for which the Oracle Multitenant option is required, the option is in use on both database instances. Additional licensing for the Oracle Multitenant option is required on all hosts within the cluster.
The Oracle Multitenant option is in use but exceeds the maximum PDB amount
In this scenario, Database Instance 1 and Database Instance 2 are running Oracle Database 12.1 Enterprise Edition. Database Instance 1 contains three user-created PDBs, while Database Instance 2 contains one user-created PDB. Database Instance 3 is running Oracle Database 18c Enterprise Edition and contains 255 user-created PDBs. Since both Database Instance 1 and Database Instance 3 exceed the minimum number of user-created PDBs for which the Oracle Multitenant option is required, the option is in use on both database instances. Additional licensing for the Oracle Multitenant option is required on all hosts within the cluster.
However, Database Instance 3 is considered to be out of compliance. Based on licensing rules for the Oracle Multitenant option, the maximum number of user-created PDBs that are supported on database instances running Oracle Database 18c Enterprise Edition is 252. Since Database Instance 3 contains 255 user-created PDBs, Software Asset Management creates removal candidates for the three additional user-created PDBs. These additional PDBs must be removed to maintain compliance.