Oracle Multitenant option use cases

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Oracle Multitenant option use cases

    The Oracle Multitenant option enables the use of pluggable databases (PDBs) within Oracle Database Enterprise Edition instances. Understanding when this option is required for licensing is critical to ensure compliance and optimize costs. This content explains typical scenarios illustrating when the Oracle Multitenant option is considered in use, when it is not, and when usage exceeds licensing limits.

    Show full answer Show less

    Key Use Cases

    • Oracle Multitenant option not in use: Instances running Oracle Database 12.1 or 18c Enterprise Edition with fewer user-created PDBs than the minimum threshold do not require additional licensing. For example, if each instance contains only one user-created PDB, the Multitenant option is not considered in use and no extra licensing is needed.
    • Oracle Multitenant option in use: When an instance contains user-created PDBs equal to or exceeding the minimum required number, the option is in use. For instance, instances with three or more user-created PDBs (Oracle 12.1) or five or more (Oracle 18c) require additional licensing on all hosts within the cluster.
    • Oracle Multitenant option exceeds maximum supported PDBs: Oracle Database 18c Enterprise Edition supports a maximum of 252 user-created PDBs per instance. Instances exceeding this limit, such as one with 255 PDBs, are out of compliance. Software Asset Management will identify excess PDBs as removal candidates, and these must be deleted to restore compliance.

    Key Outcomes

    • ServiceNow customers can use this guidance to assess their Oracle Database environments for Multitenant option licensing requirements.
    • Identifying the number of user-created PDBs per instance helps determine whether additional licensing is necessary, preventing unexpected compliance issues.
    • Awareness of the maximum supported PDB count under Oracle Database 18c prevents over-deployment and supports proactive license management.
    • Software Asset Management tools can assist in detecting compliance violations related to excessive PDBs and recommend corrective actions.

    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

    Figure 1. Oracle Multitenant option not in use example
    Oracle Multitenant option 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

    Figure 2. Oracle Multitenant option in use example
    Oracle Multitenant option 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

    Figure 3. Oracle Multitenant option in use but exceedx maximum PDB amount example
    Oracle Multitenant option in use but exceeds 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.