Oracle Multitenant Licensing
- Multitenant Option: Requires additional licensing for Enterprise Edition.
- SE2 Limitations: Only supports single-tenant architecture.
- License by Container: Each CDB requires a separate license.
- Pluggable Databases (PDBs): Additional PDBs beyond three incur fees.
- Cloud Use: Pricing differs for cloud vs. on-premises.
Oracle Multitenant Licensing
Oracle Multitenant represents a significant advancement in database management.
Allowing multiple pluggable databases (PDBs) to coexist within a single container database (CDB) offers flexibility and efficiency that greatly benefits enterprises seeking to optimize their database infrastructure.
This guide will give you an in-depth understanding of Oracle Multitenant’s licensing considerations, ensuring you are well-equipped to make informed decisions about its adoption and use.
Core Licensing Structure
Base Requirements
Oracle Multitenant is available as an add-on to the Oracle Database Enterprise Edition. It requires additional licensing fees and a standard database license.
Understanding the cost structure is crucial for budgeting and planning, especially in larger deployments.
- $17,500 per processor: This cost is applied per processor for each instance of the Oracle Database running Multitenant.
- $350 per Named User Plus (NUP): The licensing cost can be based on Named User Plus (NUP), which covers individual users accessing the database.
These costs must be added to the Enterprise Edition license costs, making careful cost-benefit analysis essential.
Free Usage Allowance
With the release of Oracle 19c, Oracle introduced a significant licensing benefit: organizations can use up to three user-created PDBs within a single CDB without requiring a separate Multitenant license.
This represents a considerable improvement over earlier versions of Oracle, which allowed only one PDB without additional licensing.
This free allowance can be extremely beneficial for smaller environments or testing purposes. However, it is important to manage the number of PDBs carefully to avoid compliance issues.
Licensing Metrics
Oracle Multitenant licensing can be approached using two primary metrics, and choosing the right one depends on the deployment environment and your organization’s specific needs.
Named User Plus (NUP)
- Covers all users and devices accessing a PDB: NUP licensing is based on the number of users and/or devices accessing the database, making it a good option for environments with a defined and limited user base.
- Minimum Requirement: Requires a minimum of 10 NUP licenses per 8 vCPUs.
- Ideal Use Case: Best suited for environments with a fixed number of users that can be accurately counted, such as internal applications with a limited number of end users.
Per Processor
- Processor licensing is based on the number of processor cores running the PDBs. This method uses Oracle’s core factor licensing rules, which adjust the number of required licenses based on the processor type.
- Processor licensing is typically a better fit for large-scale deployments with indefinite or extremely large users, such as public-facing applications.
Read about Oracle RAC Licensing.
Cloud Environment Licensing
Licensing requirements for Oracle Multitenant can vary significantly in cloud environments such as AWS and Azure.
Understanding the distinctions between cloud configurations will help ensure compliance and prevent unexpected licensing costs.
- Multi-threading Enabled: In environments where multi-threading is enabled, Oracle licensing rules dictate that two vCPUs are equivalent to one Oracle CPU license. This is an important consideration when planning cloud deployments, as it can significantly impact the number of licenses required.
- Multi-threading Disabled: If multi-threading is disabled, one vCPU equals one Oracle Processor license. This configuration is more straightforward but may require additional hardware resources.
Licensing Compliance Considerations
Compliance with Oracle’s licensing requirements is essential to avoid significant financial penalties. The three-PDB free allowance provides flexibility but introduces compliance risks that must be managed carefully.
Risk Factors
There are several risk factors associated with Oracle Multitenant licensing that organizations need to consider:
- Accidental PDB Creation: It is easy for database administrators to create additional PDBs beyond the allowed three without realizing the licensing implications. This can lead to unintentional compliance violations.
- No Technical Restriction on PDB Count: Oracle does not enforce a hard technical limit on the number of PDBs created in a CDB. This means that even though only three PDBs are allowed without licensing, there are no built-in safeguards to prevent the creation of a fourth PDB.
- Unplugging and Replugging PDBs: PDBs can be unplugged from one CDB and plugged into another. This movement between containers is not restricted by licensing controls, which can make it challenging to track PDB usage accurately.
To mitigate these risks, it is crucial to establish strong monitoring and governance practices that prevent accidental violations.
Benefits of Multitenant Architecture and Impact on Licensing
The Oracle Multitenant architecture delivers several important benefits, but these advantages also affect licensing and overall costs. Below are some of the key benefits and how they interact with licensing considerations:
- Consolidated Infrastructure: Oracle Multitenant enables significant consolidation of hardware resources by allowing multiple PDBs to reside within a single CDB. This helps reduce the number of CDBs required, leading to lower licensing costs if managed correctly.
- Simplified Management: Database management becomes simpler because administrators only need to manage one CDB that contains multiple PDBs. This centralization helps reduce administrative overhead.
- Improved Resource Utilization: The ability to share resources between PDBs leads to better overall resource utilization. However, this consolidation can also lead to more complex licensing scenarios, particularly if the PDBs serve different purposes or belong to different business units.
Read about Oracle BYOL.
Implementation Guidelines
Certain implementation guidelines and best practices should be followed to get the most out of Oracle Multitenant while staying compliant.
Best Practices for Licensing Compliance
To maximize the value of Oracle Multitenant and ensure compliance with licensing rules, consider implementing the following best practices:
- Monitor PDB Count: Regularly audit the number of PDBs in each CDB to ensure you do not exceed the free limit of three PDBs without proper licensing.
- Prevent Unauthorized PDB Creation: Implement controls to prevent unauthorized PDB creation. This could include restricting privileges to create PDBs to a small group of trusted database administrators.
- Use Resource Manager: Oracle Resource Manager should be configured to control resource allocation between PDBs, ensuring each PDB receives its required resources without causing conflicts.
Security Considerations
Security must also be a priority when implementing Oracle Multitenant:
- Access Controls: Implement strict access controls to ensure only authorized personnel can create, modify, or delete PDBs. This helps prevent unauthorized PDBs from being added.
- Data Isolation: Proper data isolation between PDBs is essential, particularly in environments where different business units or clients share a common CDB. Sensitive data should be encrypted to prevent unauthorized access.
Enterprise Deployment Scenarios
Consolidation Projects
One of the most compelling use cases for Oracle Multitenant is in large-scale database consolidation projects.
The benefits of using Oracle Multitenant for consolidation include:
- High PDB Capacity: On platforms such as Oracle Exadata and Oracle Cloud, a single CDB can support up to 4,096 PDBs. On other platforms, the limit is 252 PDBs. This capability allows for significantly reducing the number of databases in use.
- Centralized Management: Consolidation through Multitenant allows for centralized patch management across all PDBs. This means patches need only be applied once at the CDB level, which reduces downtime and administrative effort.
Development and Testing Environments
Oracle Multitenant is also particularly useful in development and testing environments. Its features can help streamline development processes and reduce costs:
- Snapshot Clones: The ability to create snapshot clones of PDBs allows development teams to quickly spin up new instances without requiring large amounts of storage. This is particularly useful for testing changes or new features in an isolated environment.
- Development vs. Production Isolation: Maintaining a strict separation between development and production environments is crucial. This helps avoid licensing complications and ensures testing does not impact live production systems.
Cost Optimization Strategies
Oracle Multitenant licensing can be costly, especially for large enterprises. Below are some strategies that can be used to optimize costs and ensure that your organization is making the most of its investment:
Evaluate Licensing Metrics
- Usage Patterns: Determine whether Named User Plus (NUP) or Processor-based licensing suits your environment. NUP licensing might be more cost-effective if you have a fixed and easily defined user base. On the other hand, if the number of users is large or indeterminate, Processor-based licensing could be the better choice.
- Consolidation Opportunities: Use the three-PDB free allowance to the fullest extent possible. By consolidating smaller databases into a single CDB, you can reduce the need for additional licenses.
Cloud Migration
- On-premises vs. Cloud: Compare the costs of keeping your Oracle database on-premises versus moving to the cloud. Cloud environments offer greater scalability and can simplify the licensing process, but they also have unique licensing requirements that must be considered.
- Hybrid Deployments: Consider a hybrid deployment that combines on-premises and cloud resources. This can help you balance costs while maintaining the flexibility and scalability needed for your databases.
Resource Consolidation
- Maximize Resource Utilization: Make sure all licensed resources are being fully utilized. Consolidate underutilized databases into fewer CDBs to maximize your existing licenses.
- Implement Monitoring and Tracking Systems: Monitoring tools are crucial for tracking PDB usage and ensuring compliance with licensing requirements. Automated tracking can help avoid costly mistakes and ensure that database usage aligns with license agreements.
Future Considerations
Architecture Evolution
Oracle is making a significant architectural shift with Oracle Database 21c:
- Multitenant Becomes the Only Supported Architecture: Starting with Oracle Database 21c, Multitenant is the default architecture. Non-container databases are no longer supported, and organizations must transition to the Multitenant model.
- Migration Planning: To prepare for this transition, organizations must start planning their migration strategies well. This includes evaluating existing databases and determining the best path forward for migrating to the new architecture.
Compliance Management
Proper compliance management is critical in preventing unexpected licensing expenses and ensuring that the organization remains in good standing with Oracle’s licensing requirements:
- Documentation: Maintain detailed records of all PDB usage, including who created each PDB, its purpose, and how it is being used. Clear documentation can help justify licensing decisions during an audit.
- Monitoring Tools: Use automated tools for PDB counting and compliance checks. These tools can help identify potential issues before they become major problems.
- Governance Policies: Establish clear policies for creating PDBs, ensuring that only authorized personnel can create new ones. Additionally, assign clear responsibilities for maintaining licensing compliance and conduct regular training sessions for database administrators.
Financial Impact of Oracle Multitenant
When considering the adoption of Oracle Multitenant, it is essential to evaluate its direct costs and indirect benefits.
This comprehensive cost analysis will help determine if Oracle Multitenant is a worthwhile investment for your organization.
Direct Costs
- License Fees: The most obvious cost is the license fee for any PDBs beyond the free limit of three. These fees can add up quickly depending on the number of processors or users.
- Support and Maintenance: Besides the licensing fees, ongoing support and maintenance costs must be factored into the budget. These costs can vary depending on the level of support purchased.
Indirect Benefits
- Reduced Hardware Requirements: By consolidating multiple databases into a single CDB, you can significantly reduce the hardware requirements for your database infrastructure. This leads to cost savings regarding physical servers, storage, and associated power and cooling.
- Lower Administrative Overhead: With fewer CDBs to manage, the overall administrative effort is reduced. Database administrators can manage multiple PDBs through a single interface, which helps save time and reduce labor costs.
- Simplified Disaster Recovery: Disaster recovery becomes more straightforward with all PDBs consolidated in a single CDB. The ability to back up and recover the entire CDB simultaneously simplifies the disaster recovery process and can reduce downtime.
FAQ: Oracle Multitenant Licensing
What is Oracle Multitenant?
Oracle Multitenant allows multiple pluggable (PDBs) to run within a single container database (CDB).
Is Oracle Multitenant included in all editions?
No, it is only fully supported in Enterprise Edition. Standard Edition 2 (SE2) supports a single PDB without additional licensing.
Do I need a separate license for each PDB?
No, the licensing applies to the container database, but additional PDBs beyond three require an extra fee.
How many PDBs are included with Enterprise Edition?
Three PDBs are included by default. Licensing more than three requires the Multitenant Option.
What is the cost of the Multitenant Option?
Pricing depends on Oracle’s policies, typically based on per-processor or Named User Plus licensing metrics.
Are there restrictions for SE2 users?
SE2 only supports single-tenant architecture with one PDB and no additional PDB licensing options.
Can Multitenant be used in Oracle Cloud?
Yes, Oracle Cloud services include Multitenant support with varying licensing costs depending on usage.
What are the benefits of Multitenant licensing?
It provides simplified database consolidation and resource allocation, improving resource sharing.
How does licensing work for hybrid environments?
Licenses are required for on-premises and cloud environments, with separate terms for each.
What happens if I exceed three PDBs without licensing?
You must purchase the Multitenant Option to comply with Oracle’s licensing terms.
Does Oracle offer discounts on Multitenant licenses?
Discounts may be available through volume licensing agreements or Oracle sales negotiations.
Is there an alternative to Multitenant for SE2 users?
SE2 users can manage separate databases but cannot use full Multitenant functionality.
Are there any additional requirements for Multitenant?
Enterprise Edition must be licensed, and additional PDBs require further licensing.
Does licensing include support?
Yes, licensing includes Oracle support, but it must remain active for updates and patches.
Can Multitenant reduce hardware costs?
Yes, consolidating databases can reduce the need for multiple servers and storage systems.
