Oracle Multitenant option use cases

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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

    This document explains licensing requirements and compliance scenarios for the Oracle Multitenant option based on the number of user-created Pluggable Databases (PDBs) within Oracle Database instances. It helps ServiceNow customers understand when additional licensing is required and how to remain compliant with Oracle’s licensing policies.

    Show full answer Show less

    Key Use Cases

    • Oracle Multitenant option not in use: When database instances contain fewer than the minimum number of user-created PDBs that trigger the Oracle Multitenant option requirement, no additional licensing is needed. For example, instances with only one user-created PDB do not require the option.
    • Oracle Multitenant option in use: When one or more database instances exceed the minimum user-created PDB threshold (e.g., three or more PDBs), the Oracle Multitenant option is considered in use. Additional licensing must be purchased for all hosts in the cluster running these instances.
    • Oracle Multitenant option in use but exceeding maximum PDB count: Oracle Database 18c Enterprise Edition supports a maximum of 252 user-created PDBs per instance. If an instance exceeds this limit (e.g., 255 PDBs), it becomes non-compliant. ServiceNow Software Asset Management identifies excess PDBs as removal candidates, which must be removed to maintain compliance.

    Practical Implications for ServiceNow Customers

    ServiceNow customers managing Oracle Database environments can use these scenarios to determine when Oracle Multitenant licensing is required and ensure compliance. Monitoring the number of user-created PDBs per database instance is critical to avoid unlicensed use or exceeding maximum allowed PDBs. Using Software Asset Management to detect and remediate compliance issues helps maintain proper licensing and avoid audit risks.

    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.