Oracle database licensing

Oracle Multitenant Licensing

Oracle Multitenant Licensing works like this:

  • Oracle Multitenant Licensing: Oracle Multitenant architecture allows a database to function as a Container Database (CDB) containing Pluggable Databases (PDBs).
  • Licensing Options: Oracle Multitenant supports two types of licensing: Named User Plus and Per Processor.
  • Changes in Oracle 19c: Starting from Oracle Database 19c, a license is required if you need four or more Pluggable Databases (PDBs) within one Container Database (CDB).
  • Costs: Multi-tenant licensing must match the quantity and metric of the database enterprise edition.

Oracle Multitenant Licensing

Oracle Multitenant licensing

Oracle Multitenant Licensing is a feature that allows multiple databases to reside within a single Oracle Database instance.

This capability optimizes and simplifies database management and operation by consolidating multiple databases into a single, manageable entity.

Key Features and Benefits

  • Container Database (CDB): A database containing multiple Pluggable Databases (PDBs), allowing centralized management.
  • Pluggable Databases (PDBs): Independently functioning databases that share the same CDB resources.
  • Resource Allocation: Prioritize and allocate resources efficiently among different PDBs.
  • Isolation and Security: Each PDB operates independently, ensuring data isolation and security.
  • Scalability: Easily add or remove PDBs based on requirements without affecting the overall system performance.

Oracle Multitenant Licensing Rules

Oracle Multitenant Licensing Rules

Overview of Licensing Requirements

Oracle Multitenant is an add-on feature exclusively available with Oracle Database Enterprise Edition (DBEE). Organizations using Multitenant to manage Pluggable Databases (PDBs) must acquire additional licenses for this feature.

The licensing metric for Multitenant must match the metric and quantity of the Enterprise Edition database license, whether licensed by Named User Plus (NUP) or by Processor.

Multitenant licensing provides flexibility, but compliance requires adhering to specific rules based on how the database is deployed and accessed.


Key Licensing Rules for Multitenant

  • Multitenant Requires Additional Licensing: The Multitenant option is not included with the base Enterprise Edition license and must be purchased separately.
  • Metric Matching: If the database is licensed by Processor, the Multitenant licenses must also be by Processor, and the quantities must match exactly. The same rule applies to Named User Plus licenses.
  • Exclusive to Enterprise Edition: Multitenant is only available for Oracle Database Enterprise Edition users. It is not supported in Standard Edition or other Oracle database offerings.

Named User Plus Licensing

  • Definition: Named User Plus (NUP) licenses are based on the number of distinct users or devices accessing the PDBs.
  • Application: This model is ideal for smaller environments with a manageable and known user base.
  • Requirements:
    • Each user and device accessing the PDBs must be accounted for and licensed.
    • If 100 users or devices access the PDBs, 100 Named User Plus licenses for Multitenant are required.
    • The total number of Named User Plus licenses for Multitenant must match or exceed the minimum required by Oracleโ€™s licensing rules for Enterprise Edition.

Processor Licensing

  • Definition: Processor licensing is based on the number of processor cores on the physical machines running the PDBs.
  • Application: This model is most suitable for environments with a large or unknown user base, where counting individual users is impractical.
  • Requirements:
    • Each processor core in the physical host must be licensed for Multitenant.
    • The Core Factor Table is applied to calculate the number of processor licenses needed. For example, using an Intel processor with a core factor of 0.5, two cores equal one processor license.
    • Multitenant must also have ten licenses if the Enterprise Edition database has ten processor licenses.

Licensing Requirements in Oracle Database 19c

Oracle Database version 19c introduced updated licensing rules for the Multitenant feature.

  1. Up to Three PDBs Without a Multitenant License:
    • Oracle permits up to three user-created PDBs within a single Container Database (CDB) without requiring a Multitenant license.
    • This exception applies only to Oracle Database Enterprise Edition.
  2. Four or More PDBs Require Licensing:
    • A Multitenant license is required if an organization runs four or more PDBs within a single CDB.
    • The licensing must cover all PDBs in the deployment, not just the ones beyond the third.

Comparison with Pre-19c Licensing Rules

In Oracle Database versions before 19c, the licensing requirements for Multitenant were stricter:

  • Single PDB Without a License: Organizations could create and use only one PDB in a CDB without a Multitenant license.
  • Licensing for Multiple PDBs: Any additional PDBs beyond the first required licensing, regardless of the total number.

With Oracle 19c, the ability to create up to three PDBs without a license has provided additional flexibility for smaller deployments.


Example Licensing Scenario

Scenario: An organization runs Oracle Database Enterprise Edition on a physical server with 16 Intel processor cores using the Processor licensing metric.

  1. Database License Requirement: The Core Factor Table for Intel processors specifies a factor of 0.5. Therefore, the organization requires eight processor licenses for the database (16 cores \ 0.5 = 8 processor licenses).
  2. Multitenant License Requirement: The organization also uses Multitenant to manage six PDBs in one CDB, exceeding the three-PDB limit. Therefore, it must license the Multitenant option.
  3. Multitenant Processor Licenses: To comply, the organization must purchase eight processor licenses for Multitenant, matching the database licensing metric and quantity.

Result: Without proper Multitenant licensing, the organization would be non-compliant and potentially subject to audit penalties.

Oracle Multitenant Licensing Costs

Oracle Multitenant Licensing Costs

Cost Structure for Multitenant Licensing

Named User Plus License Cost: A Named User Plus license costs $350 per named user. This fee covers each user and device that accesses the PDBs.

Per Processor License Cost: A Per Processor license costs $17,500 per processor. This fee is calculated based on the number of processor cores on the physical hosts running the PDBs.

Cost Calculation Examples

Step-by-Step Guide to Calculating Total Licensing Cost

  1. Determine the Number of Processor Licenses or Named Users Plus: Identify the number of processor cores, users, and devices accessing the PDBs.
  2. Apply the Cost per License: Multiply the licenses needed by the respective cost ($350 per named user or $17,500 per processor).
  3. Sum the Costs: Add the total costs from the processor licenses and named user plus licenses to get the overall licensing cost.

Example Scenario with Detailed Cost Breakdown If a company needs eight processor licenses and 100 named users plus:

  • Processor Licensing Cost: 8 processors x $17,500 per processor = $140,000
  • Named User Plus Licensing Cost: 100 users x $350 per user = $35,000
  • Total Cost: $140,000 (processors) + $35,000 (users) = $175,000

Factors Influencing Total Cost

  • Number of Processor Licenses: The higher the licensing cost, the more processor cores are used. This model scales with the computational power of the servers running the PDBs.
  • Number of Named Users Plus The total number of users and devices accessing the PDBs directly influences the licensing cost. Under this licensing model, environments with many users will see higher costs.
  • Understanding the licensing rules and cost structures, ensuring compliance, and optimizing database management strategies can help organizations make informed decisions about Oracle Multitenant licensing.

FAQ: Oracle Multitenant Licensing

What is Oracle Multitenant Licensing?

Oracle Multitenant Licensing allows multiple databases to operate within a single Oracle Database instance. This feature consolidates multiple databases into one entity, simplifying management and optimizing resources.

What are the main benefits of Oracle Multitenant Licensing?

The benefits include simplified management, better resource allocation, and improved scalability. Allowing multiple databases to share the same infrastructure reduces overhead and enhances performance.

How does the Container Database (CDB) and Pluggable Database (PDB) architecture work?

A Container Database (CDB) contains multiple Pluggable Databases (PDBs). The CDB holds the metadata and common resources, while each PDB operates independently but shares the CDBโ€™s resources.

What licensing options are available for Oracle Multitenant?

Oracle Multitenant supports Named User Plus and Per Processor licensing options. Named User Plus is based on the number of users and devices accessing the databases, while Per Processor is based on the number of processor cores on the database servers.

What is Named User Plus licensing?

Named User Plus licensing charges for each user and device that accesses a PDB. This model is ideal for environments with a defined and manageable number of users.

What is Per Processor licensing?

Per Processor licensing is based on the number of processor cores on the physical hosts running the PDBs. This model suits large-scale deployments where tracking individual users is impractical.

How many PDBs can be used without requiring a license in Oracle 19c?

In Oracle 19c, you can use up to three user-created PDBs within one CDB without needing a Multitenant license. A license is required for four or more PDBs.

How did the licensing requirements change in Oracle 19c compared to earlier versions?

Before Oracle 19c, only one user-created PDB could be used without a Multitenant license. Oracle 19c allows up to three user-created PDBs without a license, providing more flexibility.

What is the cost of a Named User Plus license for Oracle Multitenant?

A Named User Plus license costs $350 per named user. This covers each user and device accessing the PDBs.

What is the cost of a per-processor license for Oracle Multitenant?

The cost for a Per Processor license is $17,500 per processor. This fee is calculated based on the number of processor cores on the physical servers running the PDBs.

How do I calculate the total cost for Oracle Multitenant licensing?

First, determine the number of processor licenses or named users needed. Multiply the number of licenses by their respective costs. For example, eight processor licenses cost 8 x $17,500, and 100 named users cost 100 x $350. Add these amounts to the total cost.

What factors influence the total cost of Oracle Multitenant licensing?

The total cost is influenced by the number of processor licenses, named users, and the chosen licensing model (Named User Plus or Per Processor).

What are the advantages of using Per Processor licensing over Named User Plus?

Per-processor licensing is advantageous for large-scale deployments where managing individual user licenses is difficult. It simplifies licensing by focusing on processor cores rather than user count.

Why might an organization choose Named User Plus licensing?

Named User Plus licensing is suitable for organizations with a well-defined user base. It allows precise cost management based on the number of users and devices accessing the PDBs.

Can Oracle Multitenant be used in a cloud environment?

Yes, Oracle Multitenant can be used in cloud environments. It supports cloud infrastructure, enabling efficient database consolidation and management while ensuring compliance with licensing requirements.

Do you want to know more about our Oracle License Management Services?

Please enable JavaScript in your browser to complete this form.
Author
  • Fredrik Filipsson has 20 years of experience in Oracle license management, including nine years working at Oracle and 11 years as a consultant, assisting major global clients with complex Oracle licensing issues. Before his work in Oracle licensing, he gained valuable expertise in IBM, SAP, and Salesforce licensing through his time at IBM. In addition, Fredrik has played a leading role in AI initiatives and is a successful entrepreneur, co-founding Redress Compliance and several other companies.

    View all posts