Oracle Multitenant Licensing
- Oracle Multitenant: Requires separate licensing
- Container Databases (CDBs): Included with Oracle Database
- Pluggable Databases (PDBs): Additional cost after three PDBs
- Standard Edition: No Multitenant feature
- Enterprise Edition: Multitenant available as a paid option
- Deployment: One CDB with up to three free PDBs
Oracle Multitenant Licensing
What is Oracle Multitenant?
Oracle Multitenant is a database architecture introduced in Oracle Database 12c. It allows multiple pluggable (PDBs) to run inside a single container database (CDB), allowing you to manage several databases as one unit and significantly simplifying administrative tasks.
Key Features of Oracle Multitenant:
- Container Database (CDB): The base structure that hosts multiple pluggable databases.
- Pluggable Databases (PDBs): Self-contained databases that plug into a CDB, making resource management more efficient.
- Rapid Cloning and Patching: Enables faster updates by patching the CDB, impacting all PDBs simultaneously.
Oracle Multitenant is ideal for consolidating databases, reducing the complexity of managing multiple systems, and saving maintenance costs.
Licensing Options for Oracle Multitenant
Understanding Oracle’s Multitenant licensing is crucial for effective budgeting and compliance. Here are the primary licensing options to consider:
1. Oracle Database Standard Edition 2 (SE2)
- Support for PDBs: Oracle SE2 allows only a single PDB. This feature is included in the Oracle Database SE2, so you do not need a separate license.
- Limitations: SE2 is limited to smaller workloads because it only supports one PDB suitable for small businesses or development environments.
- Cost: SE2 offers an affordable choice since the licensing fees are lower but minimal in scalability.
2. Oracle Database Enterprise Edition (EE)
- Support for PDBs: By default, EE allows you to run up to three PDBs without an additional licensing fee. This is great for companies with minimal consolidation needs.
- Licensing Beyond Three PDBs: If you need more than three PDBs, you will require the Oracle Multitenant Option, which adds high cost and substantial scalability.
- Use Cases: Enterprise Edition suits medium—to large companies with scalability requirements and more complex workloads.
3. Oracle Multitenant Option for Enterprise Edition
- Unlimited PDBs: This option allows you to run up to 4096 PDBs within a CDB.
- Additional Costs: This requires licensing the Oracle Multitenant Option, which is typically charged per processor. This can be expensive, especially in large setups.
- Benefits: This option is ideal for massive database consolidation, cloud deployments, and larger environments where managing multiple databases in separate instances would otherwise be cumbersome.
Cost Breakdown: What to Expect
Oracle’s Multitenant licensing costs can add up quickly depending on your chosen configuration. Here is a breakdown:
1. Core Licensing Costs
- Enterprise Edition (EE): The cost for EE is often calculated per processor or named user. Oracle’s pricing depends on your hardware configuration.
- Oracle Multitenant Option: This is an add-on cost to the EE license and is also charged per processor.
For example:
- If you have an EE license that costs around $47,500 per processor and wants the Multitenant Option, which may add around $17,500 per processor, the total licensing costs can become significant.
2. Processor-Based vs. User-Based Licensing
- Processor-Based Licensing: This type of licensing is typically used for high-scale environments where the number of users is very large or unpredictable.
- User-Based Licensing: This is a cheaper alternative if the number of users is known and limited. However, it is rarely used in environments that benefit from Multitenant architecture due to scalability needs.
3. Support and Maintenance Fees
Oracle also charges annual support and maintenance fees, typically around 22% of the license cost. These fees cover updates, patches, and access to Oracle’s support services.
Practical Examples of Multitenant Licensing Costs
Consider these scenarios to understand the cost implications better:
Scenario 1: Small Business with Oracle SE2
- Requirement: 1 PDB for an application database.
- License: Oracle SE2 (includes 1 PDB).
- Cost: License costs are relatively low, and the Multitenant Option has no additional fees. It is ideal for development or small-scale production use.
Scenario 2: Mid-size company with EE
- Requirement: 3 PDBs to consolidate multiple applications.
- License: Oracle EE without the Multitenant Option.
- Cost: The standard EE license could cost around $47,500 per processor. Since the requirement is only for 3 PDBs, no additional Multitenant Option costs exist.
Scenario 3: Large Enterprise with Complex Needs
- Requirement: 50 PDBs for a cloud solution consolidating numerous databases.
- License: Oracle EE with the Multitenant Option.
- Cost: You need the standard EE license plus the Multitenant Option. For 50 PDBs, the price per processor can be around $47,500 + $17,500 for the Multitenant Option, which multiplies based on the number of processors required.
Key Considerations When Choosing a Licensing Model
Before deciding on an Oracle Multitenant licensing model, consider these essential points:
1. Number of PDB Required
- For up to 3 PDBs, stick with Oracle EE without the Multitenant Option.
- If you need more than 3 PDBs, the Multitenant Option is necessary.
2. Future Scalability
- SE2 is cost-effective but does not have scaling ability. If you anticipate growth, starting with EE may save you from costly migrations later.
3. Hardware and Processor Costs
- Since Oracle pricing is often processor-based, understanding your hardware setup is critical. Consolidating PDBs on fewer processors can reduce licensing costs, but it may also impact performance.
4. Cloud vs. On-Premise
- Oracle’s Multitenant architecture works well in cloud environments. Licensing in the cloud can be more flexible, especially with Oracle Cloud’s BYOL (Bring Your License) programs.
5. Compliance and Audits
Oracle is known for being strict about compliance. When consolidating multiple PDBs, it’s crucial to maintain a detailed record of your PDB deployments and the licenses associated with them. Non-compliance can lead to hefty fines, so keep your licensing documentation accurate and up to date. Regularly conduct internal audits to ensure you align with Oracle’s licensing terms.
6. Cost vs. Value
The licensing costs of Oracle Multitenant can be substantial, but the potential value it offers in terms of reduced administrative workload, simplified updates, and efficient consolidation is significant. When deciding, weigh the total cost against the operational savings you may realize over time. The more PDBs you need to manage, the greater the value Oracle Multitenant brings.
Detailed Overview of Multitenant Deployment Scenarios
Deploying Oracle Multitenant involves numerous configurations, each with advantages and cost implications.
Below, we examine potential deployment scenarios to understand where Oracle Multitenant licensing makes the most sense.
Scenario 4: Hybrid Cloud Deployment
- Requirement: A company with a combination of on-premises and cloud databases needs a centralized management system for better integration.
- License: Oracle EE with Multitenant Option and Oracle Cloud BYOL.
- Cost: On-premises costs include $47,500 for EE and $17,500 per processor for the Multitenant Option, plus cloud licensing fees.
- Benefits: The hybrid approach provides flexibility, allowing the company to store sensitive data on-premises while moving less critical data to the cloud. The Multitenant architecture allows seamless cloning and movement between the cloud and on-premises environments.
Scenario 5: SaaS Provider with High Consolidation Needs
- Requirement: A Software-as-a-Service (SaaS) provider must efficiently manage hundreds of client databases.
- License: Oracle EE with Multitenant Option to support hundreds of PDBs.
- Cost: Given the scale, licensing costs may involve multiple processors, totaling $47,500 + $17,500 per processor multiplied by the number of processors needed.
- Advantages: This model allows the SaaS provider to centrally manage hundreds of client databases while providing high availability and disaster recovery features across all PDBs. High-density consolidation makes Oracle Multitenant a cost-effective choice despite high upfront costs.
Read about Oracle Database License Management Tools.
Strategies for Effective Oracle Multitenant Utilization
1. Effective PDB Consolidation Planning
Proper planning during the consolidation phase can lead to significant cost savings. When deciding which databases to consolidate into PDBs, consider their usage patterns, peak load times, and criticality. Combining databases with complementary workloads can help maximize resource utilization and minimize the need for additional processors, thereby reducing licensing fees.
2. Leverage Resource Manager
Oracle’s Database Resource Manager can effectively allocate resources among PDBs. This is particularly useful in preventing a single PDB from monopolizing the CPU or I/O, which could impact performance and necessitate additional processors. Balancing resource use allows you to stay within the licensing limits and avoid extra costs.
3. Use Snapshot Clones for Development and Testing
One helpful feature of Oracle Multitenant is Snapshot Cloning. This allows you to create a read-write clone of an existing PDB for development, testing, or troubleshooting purposes. Since these clones share data blocks with the original PDB, they require less storage, and their rapid provisioning can save time and resources. Leveraging snapshot clones reduces the need for wholly duplicated environments, optimizing costs.
4. Multitenant on Oracle Cloud
Oracle Multitenant is highly compatible with Oracle Cloud Infrastructure (OCI). Utilizing Multitenant in a cloud environment provides flexible pricing options, and Oracle’s Autonomous Database even includes features that automate much of the manual management typically required. If you’re currently using an on-premises deployment, transitioning to OCI can reduce ongoing maintenance costs while benefiting from Oracle’s cloud licensing discounts.
The Role of Oracle Partitioning with Multitenant
Incorporating Oracle Partitioning alongside Multitenant can be a game-changer, especially for enterprises managing vast data sets. Partitioning allows you to divide large tables into smaller, more manageable pieces, improving query performance and reducing maintenance time. Combining Partitioning with Multitenant offers substantial performance improvements when dealing with consolidated PDBs that host large volumes of data. However, it is essential to note that Oracle Partitioning is a separately licensed option, meaning additional costs must be factored in.
- Scenario Example: Consider a retail company managing separate PDBs for different regional sales databases. By partitioning, the company can divide transactional data into segments based on date or geographical location, making queries faster and reporting more efficient. While this adds another layer of licensing, the performance gains may outweigh the cost, particularly in data-intensive environments.
Monitoring and Optimization Tips
1. Use Oracle Enterprise Manager (OEM)
Oracle Enterprise Manager is critical for monitoring PDBs and ensuring efficient performance. Using OEM can help in:
- Tracking the resource usage of each PDB.
- Setting alerts for when resource consumption exceeds predefined thresholds.
- Identifying underutilized resources that can be repurposed, potentially reducing the number of processors and associated licensing costs.
2. Regular Performance Tuning
Regular performance tuning can help avoid unnecessary licensing costs. If certain PDBs are performing poorly, they may require additional processors, increasing your licensing obligations. Regularly tune:
- SQL queries to ensure they are optimized.
- Indexes to improve retrieval times and reduce CPU usage.
- Memory allocation to minimize swap and improve efficiency.
3. Review PDB Workloads Periodically
Workloads can change over time, and what made sense a year ago might not be optimal today. Periodic reviews can help you determine whether certain PDBs can be decommissioned or combined with others, thus reducing licensing costs.
Oracle Multitenant Licensing FAQ
What is Oracle Multitenant Licensing?
Oracle Multitenant licensing is an option for managing multiple databases within a single container database (CDB) structure.
Is Multitenant included in the Oracle Database by default?
It’s included, but full Multitenant capabilities require a separate license for more than three pluggable databases (PDBs).
How many free PDBs can I have without licensing?
You can have up to three PDBs for free in one CDB; additional PDBs need licensing.
Does Oracle Standard Edition include Multitenant?
No, Multitenant is only available with Oracle Database Enterprise Edition.
Is Multitenant necessary for Oracle Database 19c or later?
Oracle Database 19c and later support Multitenant, but using more than three PDBs requires a license.
How much does an Oracle Multitenant license cost?
Pricing can vary, so contact Oracle for exact costs. It depends on factors like the number of PDBs and deployment type.
Can I use Multitenant for free in any Oracle setup?
Yes, Enterprise Edition includes up to three PDBs for free; more than three require a license.
Is a separate license needed for each PDB?
No, licensing is per CDB, which covers multiple PDBs within the same CDB.
What is a Pluggable Database (PDB)?
A PDB is a database that runs within a container database, providing isolated resources.
Can I mix licensed and free PDBs in one CDB?
No, exceeding three PDBs in a single CDB requires licensing all PDBs.
Does every CDB require a license?
Yes, every CDB with more than three PDBs needs a Multitenant license.
Are there discounts for large Multitenant deployments?
Oracle may offer discounts for large setups. Contact Oracle for tailored pricing.
What Oracle support level is needed for Multitenant?
Standard support applies, but higher support levels may be recommended for large deployments.
What happens if I exceed three PDBs without licensing?
Using more than three PDBs without licensing can lead to non-compliance issues.
Can I downgrade from Enterprise Edition to Standard?
Yes, but Standard Edition does not support Multitenant, so PDBs will not function as they do in Enterprise.
