Oracle Database Licensing

Oracle Database Licensing

• Two main types: Per processor and Named User Plus (NUP).
• Processor licensing: Based on cores, uses Oracle Core Factor table.
• NUP licensing: Based on the number of users or devices accessing.
• Virtualization: Rules differ for VMware, OVM, and cloud setups.

Oracle Database License Types

Oracle offers several licensing models for its database products, each designed to accommodate different usage scenarios and organizational needs.

The two primary license types are:

Processor Licensing

This model is ideal for environments where counting individual users is impractical, such as web-based applications or large-scale enterprise deployments. Processor licensing requires organizations to license all processor cores in the server or cluster where Oracle Database is installed or running.

• Core-Based Calculation:
  • The number of required licenses is calculated by multiplying the total number of cores by a specific core factor determined by Oracle.
  • Example: A server with eight cores and a core factor of 0.5 would require four processor licenses.

Named User Plus (NUP) Licensing

NUP licensing is based on the number of individuals or devices accessing the database. This model is more suitable for environments with a clearly defined and limited user base, such as development teams or small departments.

• Minimum License Requirement:
  • Each NUP license covers a minimum number of users per server or processor, which varies depending on the Oracle Database edition in use.
  • Example: An Oracle Enterprise Edition server may require at least 25 NUP licenses per processor.

Specialized Licensing Options

In addition to the primary models, Oracle offers specialized licensing options tailored to specific scenarios:

• Cloud BYOL (Bring Your Own License):
  • Enables customers to use their existing on-premises Oracle licenses in cloud environments.
  • Provides cost savings and flexibility for organizations transitioning to cloud infrastructure.
• Application-Specific Licensing (ASFU):
  • Restricted licenses sold by Oracle Solution Providers for use exclusively with specific third-party application packages.
• Unlimited License Agreement (ULA):
  • Designed for large enterprises, ULAs allow unlimited use of specified Oracle products for a fixed term, after which usage can be declared and converted to standard licensing.
• Embedded Software License (ESL):
  • A highly restrictive license permits Oracle software to be used only within the context of a larger software solution and without customization.

Licensing for Oracle Standard Edition

Oracle Database Standard Edition 2 (SE2) is designed for small to mid-sized businesses and offers a cost-effective alternative to Enterprise Edition.

Key Features of SE2 Licensing

• Socket-Based Licensing:
  • Licensed based on the number of occupied processor sockets rather than individual cores, offering significant cost savings.
• Server Limitations:
  • Limited to deployment on servers with a maximum of two processor sockets.
• Named User Plus Minimums:
  • Requires a minimum of 10 Named User Plus licenses per server.
• Virtualization Constraints:
  • When deployed in virtualized environments, the entire physical server must be licensed, regardless of the number of virtual CPUs allocated to the database.
• Feature Restrictions:
  • Lacks advanced features available in Enterprise Edition, such as Real Application Clusters (RAC) from Oracle Database 19c onwards.

Licensing Considerations for SE2

• Cost-Effectiveness:
  • Ideal for smaller deployments or organizations with limited database requirements.
• Scalability Limitations:
  • The two-socket limit and absence of advanced scaling features like RAC may restrict future growth.
• Upgrade Paths:
  • Older Standard Edition versions (SE or SE1) cannot coexist with SE2. Organizations may need to upgrade all instances to SE2 or move to Enterprise Edition.
• Cloud Deployments:
  • SE2 is available in Oracle Cloud Infrastructure (OCI) and Authorized Cloud Environments (ACEs).

Licensing for Oracle Enterprise Edition

Oracle Database Enterprise Edition (EE) is the most feature-rich version, designed for large enterprises and mission-critical applications that require advanced capabilities.

Key Aspects of EE Licensing

• Core-Based Licensing:
  • Requires licensing for all processor cores, with a specific core factor applied to determine the total license count.
• Named User Plus Option:
  • Organizations can opt for NUP licensing with a minimum requirement of 25 Named User Plus licenses per processor.
• Flexible Deployment:
  • It can be deployed on servers of any size without socket limitations imposed on SE2.
• Additional Options and Packs:
  • Supports a wide range of additional features through separately licensed options and management packs, including:
    • Real Application Clusters (RAC)
    • Partitioning
    • Advanced Security
    • Advanced Compression
    • In-Memory Database

Virtualization Support

EE offers greater flexibility in virtualized environments. However, specific rules apply:

• Soft Partitioning:
  • Supported with certain technologies, but all physical cores must be licensed if Oracle does not approve partitioning methods.

Licensing Considerations for EE

• Cost Factors:
  • SE3 is more expensive than SE2, especially when additional options and packs are included. Core-based licensing can lead to substantial costs for large, multi-core servers.
• Scalability and Performance:
  • Suitable for high-volume OLTP applications, large data warehouses, and demanding web applications.
• Cloud and Hybrid Deployments:
  • Available for on-premises, Oracle Cloud Infrastructure (OCI), and Authorized Cloud Environments (ACEs).
  • Oracle Base Database Service tiers provide tailored solutions:
    • Enterprise Edition
    • Enterprise Edition – High Performance
    • Enterprise Edition – Extreme Performance
• Compliance Complexity:
  • Managing the variety of options and packs can increase compliance challenges. Organizations must carefully track feature usage to avoid license violations.
• Disaster Recovery:
  • Licensing requirements depend on whether the secondary environment is active or passive. Passive standby databases do not typically require additional licenses, except during disaster events or testing (up to 10 days per year).

Oracle Autonomous Database Licensing

Oracle Autonomous Database offers flexible licensing models to cater to diverse organizational needs. The primary licensing options are Pay-As-You-Go (PAYG) and Bring Your Own License (BYOL).

Pay-As-You-Go (PAYG)

• Charges Based on Resource Consumption:
  • PAYG billing is determined by the resources consumed, such as computing power, storage, and additional services.
  • Organizations only pay for the specific resources used, eliminating unnecessary overhead costs.
• Ideal for Fluctuating Workloads:
  • Best suited for environments with unpredictable or varying workloads where resource requirements may change frequently.
  • Enables businesses to scale their resources up or down depending on operational needs.
• Billing Frequency:
  • Monthly billing is based on resource usage.
  • Customers receive detailed usage reports, aiding in transparent cost management.
• Flexible Options:
  • Available as standard Pay-As-You-Go or with an Annual Commitment option for customers seeking longer-term cost predictability.
  • Annual Commitment plans may offer discounted rates for consistent usage.

Bring Your Own License (BYOL)

• Utilizes Existing Licenses:
  • Customers can apply their existing Oracle software licenses to Oracle Cloud services, significantly reducing costs.
  • BYOL supports seamless integration with pre-owned licenses, simplifying transitions to cloud services.
• Cost Savings:
  • BYOL can lower Autonomous Database compute costs by up to 76% compared to PAYG.
  • This model allows organizations to maximize the value of their previous investments in Oracle software.
• Applicable Editions:
  • Supports Oracle Database Enterprise Edition and Standard Edition licenses.
  • Facilitates easy migration for organizations already leveraging Oracle databases.

Licensing Requirements

• Enterprise Edition:
  • It requires one processor license or 25 Named User Plus (NUP) licenses for every 2 vCPUs or two OCPUs of Autonomous Database usage.
  • Offers flexibility for large-scale enterprise deployments.
• Standard Edition:
  • Ideal for small to medium-sized businesses with less intensive database needs.

Deployment Options

• Cloud or On-Premises:
  • Autonomous Database is available on Oracle Cloud or via Exadata Cloud@Customer for on-premises deployments.
  • Provides flexibility for organizations with diverse infrastructure requirements.
• Specialized Services:
  • It supports autonomous transaction processing (ATP) and autonomous data warehouse (ADW) for versatile use cases.
  • These services cater to specific workloads, such as analytics for ADW and transaction processing for ATP.

Licensing by CPU vs Core

Oracle employs distinct licensing models for Enterprise Edition (EE) and Standard Edition (SE), with a significant difference in how CPUs and cores are accounted for.

Enterprise Edition (EE) Licensing

• Core-Based Model:
  • Licensing is based on processor cores, with a multiplier applied according to Oracle’s core factor table.
  • This model ensures fair pricing based on hardware capabilities.
• Formula:
  • Number of Cores × Core Factor = Processor License Requirement.
  • Example: A server with 16 cores and a core factor 0.5 requires eight processor licenses.

Standard Edition (SE) Licensing

• Socket-Based Model:
  • Licensing is based on the number of processor sockets rather than individual cores.
  • Offers a simpler and cost-effective approach for smaller-scale deployments.
• Feature Constraints:
  • SE licenses come with feature limitations and stricter deployment rules than EE licenses.
  • These constraints ensure that SE remains affordable for businesses with basic database requirements.

Core Factor Table

The core factor table determines licensing requirements based on processor type. Common values include:

• Intel x86 Processors: Core Factor = 0.5
• AMD Processors: Core Factor = 0.5
• IBM POWER Processors: Core Factor = 1.0

Example Calculation (EE)

For a server with 2 CPUs, each with eight cores (total 16 cores), using Intel processors:

• 16 cores × 0.5 core factor = 8 processor licenses required.
  • This calculation simplifies budgeting for large-scale enterprise environments.

Oracle Database Licensing for VM

Licensing Oracle Database in virtualized environments varies depending on the virtualization technology used.

Compliance is crucial to avoid costly penalties during audits.

Oracle VM (OVM)

• Hard Partitioning:
  • Allows licensing based on cores allocated to the virtual machine (VM) running Oracle software.
  • Provides a cost-efficient licensing method compared to soft partitioning.
  • Example: Only two licenses are required if four virtual cores are allocated to a VM and the core factor is 0.5.

VMware Environments

• Dependent on VMware Version:
  • Licensing rules differ for vSphere ESXi 5.1 and later versions.
  • These rules require careful planning to ensure compliance.
• vCenter Scope:
  • All physical cores of all ESXi hosts within the same vCenter Server instance must be licensed, even if Oracle software is running on only a subset of those hosts.
  • Example: If a vCenter Server manages ten hosts, all cores across those hosts must be accounted for.
• Cross Data Center Licensing:
  • Includes hosts across data centers connected within the same vCenter Server instance.
  • This approach ensures consistency in licensing across geographically distributed infrastructure.

Licensing Calculation in Virtual Environments

• Hard Partitions (e.g., OVM):
  • Number of virtual cores × Core Factor = Licenses Required.
  • This method minimizes licensing costs by focusing on allocated resources.
• Soft Partitions (e.g., VMware ESX):
  • Number of physical processors × Cores per Processor × Core Factor = Licenses Required.
  • This approach typically results in higher licensing requirements compared to hard partitioning.

Example Calculation (Soft Partitioning)

For a VMware environment with two processors, each with four cores:

• 2 processors × 4 cores/processor × 0.5 core factor = 4 licenses required.
  • Accurate calculations like this help organizations budget for virtualized deployments effectively.

Compliance Best Practices

• Accurate Documentation:
  • Maintain detailed records of VM configurations and changes to ensure compliance with Oracle’s licensing rules.
  • Regularly update the documentation to reflect the current infrastructure.
• Audit Readiness:
  • Regularly review configurations and licensing requirements to prepare for potential Oracle audits.
  • Proactive preparation minimizes risks of non-compliance penalties.

Database Licensing for Non-Production Environments

Oracle’s licensing policy for non-production environments, including development and testing, requires full licensing similar to that of production environments.

This approach ensures consistency across all database deployments within an organization.

Key Points for Non-Production Environment Licensing

• Full Licensing Requirement:
  • All environments where Oracle software is installed or running must be fully licensed, regardless of their purpose.
• No Differentiation:
  • Oracle does not distinguish between production, development, or non-production environments in terms of licensing requirements.
• Transition Flexibility:
  • Fully licensing non-production environments allows for a seamless transition to production use when necessary.
• Compliance Importance:
  • Proper licensing of non-production environments is crucial to avoid potential compliance issues during audits.

Licensing Options for Non-Production Environments

• Use Regular Production Licenses:
  • Organizations can use standard production licenses for non-production environments, offering flexibility to interchange entitlements between production and non-production use.
• Specific Non-Production Licenses:
  • Oracle offers licenses tailored for non-production use, which can be more cost-effective for organizations with extensive development and testing needs.
• Named User Plus (NUP) Licensing:
  • NUP licensing might be more economical for environments with limited users, such as small development teams.

Disaster Recovery Testing

• Oracle permits limited testing of disaster recovery (DR) environments for up to 10 days per year.
• Organizations should document each testing event, including start and end dates, to demonstrate compliance during audits.

Oracle Database BYOL

Oracle’s Bring Your Own License (BYOL) program allows customers to leverage their existing on-premises licenses in cloud environments, offering potential cost savings and deployment flexibility.

Key Aspects of Oracle Database BYOL

• Eligible License Types:
  • Full-Use Licenses: Allows full product usage and is the most common type.
  • Application-Specific Full-Use (ASFU) Licenses: Limited to use with specific applications.
  • Proprietary Application Hosting Licenses: Require special approval through an ISV amendment.
• Active Support Requirement:
  • Licenses used for BYOL must have an active support agreement.
• Transition Period:
  • Oracle allows 100 days for simultaneous on-premises and cloud usage during the transition to BYOL.
• Cost Savings:
  • BYOL can reduce Autonomous Database compute costs by up to 76%.
• License Conversion:
  • One processor license or 25 Named User Plus licenses of Oracle Database Enterprise Edition typically convert to 2 Oracle Compute Units (OCPUs) in Oracle Cloud.

BYOL for Autonomous Database

• Supported Editions:
  • Supports both Enterprise Edition and Standard Edition licenses.
• Standard Edition BYOL Limitations:
  • Limited to a maximum of 32 ECPUs or 8 OCPUs per instance.
• Additional Features:
  • Includes additional features and options without extra licensing requirements.

Cloud Mapping for BYOL

License Type	Cloud Mapping
Enterprise Edition Processor	1 Processor License = 2 OCPUs
Standard Edition	1 License = 4 OCPUs
Named User Plus	1 OCPU per 25 Named Users

Database License Metric Requirements

Oracle employs various metrics to determine licensing requirements for its database products. Understanding these metrics is crucial for accurate licensing and cost management.

Primary License Metrics

• Processor-Based Licensing:
  • Used for server-based products like Oracle Database.
  • Based on the number of processor cores in the server.
  • Utilizes Oracle’s core factor table to calculate required licenses.
• Named User Plus (NUP) Licensing:
  • Based on the number of individuals or devices accessing the database.
  • Suitable for environments with a clearly defined user base.

Processor Core Factor

• Adjusts license requirements based on processor type.

Processor Type	Core Factor
Intel x86 Processors	0.5
AMD Processors	0.5
IBM POWER Processors	1.0

Calculation Examples

• Processor-Based Licensing:
  • For a server with 2 CPUs, each having eight cores (16 cores total), using Intel processors:
    • 16 cores × 0.5 core factor = 8 processor licenses required.
• Named User Plus Licensing:
  • Enterprise Edition: Minimum of 25 NUP licenses per processor.
  • Standard Edition 2: Minimum of 10 NUP licenses per server.

License Metric Requirements for Different Editions

• Enterprise Edition (EE):
  • Licensed by processor cores.
  • Calculation: Number of Cores × Core Factor = Processor License Requirement.
• Standard Edition (SE):
  • Licensed by processor sockets rather than cores.
  • Subject to stricter deployment constraints.

Virtualization Considerations

• Oracle VM (OVM):
  • Allows licensing based on cores allocated to the VM.
• VMware Environments:
  • Typically, licensing all physical cores in the ESXi cluster is required.

Oracle Database Licensing for Testing

Oracle’s licensing policy for testing environments aligns with its general approach to non-production environments, requiring full licensing similar to production deployments.

Key Considerations for Testing Environment Licensing

• Full Licensing Requirement:
  • Testing environments must be fully licensed, regardless of their non-production status.
• License Type Flexibility:
  • Organizations can choose between processor-based or Named User Plus licensing depending on their testing setup and requirements.
• Optimization Opportunities:
  • Proper licensing strategies for testing environments can help optimize costs while maintaining compliance.
• Transition Readiness:
  • Fully licensed testing environments can seamlessly transition to production use when necessary.

Licensing Strategies for Testing Environments

• Processor-Based Licensing:
  • Suitable for large-scale testing environments or when user counts are difficult to determine.
  • Requires licensing of all processor cores where the database is installed or running.
• Named User Plus Licensing:
  • Appropriate for testing environments with a limited number of users.
  • It requires meeting minimum NUP requirements or licensing the actual user count, whichever is greater.
• Use of Non-Production Specific Licenses:
  • Oracle offers licenses tailored for non-production use, which can be more cost-effective for dedicated testing environments.

Special Considerations for Testing

• Disaster Recovery Testing:
  • Oracle permits testing physical copies of backups on an unlicensed computer up to 10 times in a calendar year, not exceeding one day per testing.
• Failover vs. Switchover:
  • In case of a switchover (planned role reversal between primary and DR sites), Oracle requires full licensing for both environments during the switchover period.
  • During an unplanned failover, licensing requirements for the primary site must be met once the DR system takes over.
• Documentation:
  • Maintain detailed records of testing environment configurations and any changes to ensure compliance during audits.
• Regular Review:
  • Periodically assess testing environment usage and adjust licensing to avoid over-licensing while maintaining compliance.

Oracle Database ULA

Oracle Database Unlimited License Agreement (ULA) is a flexible licensing model that allows organizations to deploy unlimited licenses for specific Oracle products over a fixed term, typically three to five years.

This approach caters to businesses with substantial and growing database requirements, offering scalability and predictability.

Key Features of Oracle Database ULA

• Unlimited Deployments:
  • Organizations can deploy as many licenses as needed during the ULA term without incurring additional costs. This feature is especially beneficial for rapidly scaling IT environments.
• Fixed Upfront Cost:
  • A one-time, fixed payment ensures predictable budgeting and simplifies financial planning for the duration of the agreement.
• Certification Process:
  • At the end of the ULA term, organizations must undergo a formal certification process to document all deployed licenses, ensuring clarity and compliance.
• Perpetual Licenses:
  • After the certification process, all deployed licenses are converted to perpetual licenses, allowing organizations to retain them indefinitely without additional costs.

Benefits of Oracle Database ULA

• Scalability:
  • It is ideal for organizations experiencing rapid growth or uncertain future needs, as it accommodates unlimited database deployments without incremental licensing costs.
• Simplified License Management:
  • Eliminates the need to track individual licenses during the ULA term, reducing administrative overhead and non-compliance risk.
• Cost Predictability:
  • Fixed costs over the agreement period ensure consistent budgeting and eliminate unexpected expenses related to database expansions.

ULA Management Considerations

• Deployment Tracking:
  • Maintain detailed records of all deployments throughout the ULA term to facilitate an accurate and efficient certification process.
• Certification Preparation:
  • Organizations should proactively prepare for the certification process, ensuring all deployments are documented and compliant with ULA terms.
• Future Needs Evaluation:
  • Assess the organization’s database growth and usage patterns before renewing the ULA, transitioning to standard licensing, or exploring alternative models.

Oracle Multitenant Licensing

Oracle Multitenant introduces a modern architecture that allows a single container database (CDB) to host multiple pluggable databases (PDBs), streamlining database management and resource utilization.

Key Aspects of Oracle Multitenant Licensing

• Enterprise Edition Option:
  • Multitenant is an add-on feature available exclusively for Oracle Database Enterprise Edition, providing advanced capabilities for database consolidation.
• Licensing Metrics:
  • Organizations can choose between two metrics: Named User Plus (NUP) or Per Processor, offering flexibility based on deployment needs.
• Cost:
  • $17,500 per processor or $350 per Named User Plus (NUP), making it a premium option for businesses seeking robust database management capabilities.

Licensing Rules

• Oracle 19c and Later:
  • Up to three user-created PDBs can be deployed without requiring an additional Multitenant license, allowing for moderate consolidation.
  • Deploying four or more PDBs necessitates the purchase of a Multitenant license.
• Pre-19c Versions:
  • These versions permit only one user-created PDB without additional licensing, limiting consolidation potential.

Licensing Considerations

• Metric Matching:
  • Ensure that the chosen licensing metric aligns with the Enterprise Edition database metrics.
• Core Factor Application:
  • Apply Oracle’s core factor rules when calculating processor-based licensing to ensure accurate compliance.
• Minimum NUP Licenses:
  • For Named User Plus licensing, a minimum of 10 NUP licenses is required for every two vCPU.

Oracle RAC Licensing

Oracle Real Application Clusters (RAC) enhances database performance and availability by allowing multiple servers to run Oracle RDBMS software simultaneously, ensuring redundancy and scalability.

Key Aspects of Oracle RAC Licensing

• Licensing Options:
  • Available under two metrics: Processor-based and Named User Plus (NUP), providing flexibility for different deployment scenarios.
• Cost:
  • $23,000 per processor.
  • $460 per Named User Plus license, reflecting the premium value of RAC’s high-availability features.

Licensing Rules

• Cluster Licensing:
  • Every node in the RAC cluster must have a valid Oracle RAC license to ensure compliance and full functionality.
• Metric Matching:
  • RAC licensing must match the licensing metric and quantity of the underlying Oracle Database Enterprise Edition.
• Core Factor Application:
  • Utilize the Oracle Core Factor Table to determine the licensing requirements for processor-based deployments.

Licensing Considerations

• Processor Calculation:
  • Calculate the number of processors across all cluster nodes to determine the licensing requirements.
• Support Costs:
  • Account for additional support and maintenance costs, which can significantly impact the total cost of ownership.
• Cloud Compliance:
  • Ensure RAC licensing compliance in cloud environments, as these deployments often have unique requirements.

Oracle Database Cloud Licensing

Oracle offers a range of cloud licensing models to cater to various deployment needs, providing flexibility and scalability for modern IT environments.

Key Cloud Licensing Options

• Universal Cloud Credits (UCCs):
  • Offers a flexible credit system that can be applied across multiple Oracle Cloud services, ensuring efficient resource utilization.
• Software as a Service (SaaS):
  • Provides fully managed access to Oracle Database capabilities, eliminating the need for on-premises infrastructure and maintenance.
• Bring Your Own License (BYOL):
  • Enables organizations to apply existing on-premises licenses to Oracle Cloud, leveraging prior investments to reduce costs.

Cloud Licensing Features

• Scalability:
  • Resources can be scaled dynamically based on demand, providing cost and performance optimization.
• Pay-as-You-Go:
  • Flexible usage-based billing models ensure cost efficiency by charging only for actual resource consumption.
• Subscription-Based:
  • Predictable recurring costs through subscription plans simplify budgeting for long-term deployments.

Licensing Considerations

• Deployment Strategy:
  • Evaluate which cloud licensing model best aligns with organizational objectives, workload requirements, and budget constraints.
• BYOL Advantages:
  • Utilize existing licenses to significantly lower cloud deployment costs and enhance ROI.
• Cost Analysis:
  • To determine the most cost-effective solution, assess the implications of different pricing structures, such as pay-as-you-go, subscription, and universal credit models.

By understanding and optimizing these licensing models, organizations can make well-informed decisions that effectively balance cost, performance, and scalability to support their Oracle database deployments.

Oracle Database Usage-Based Licensing

Oracle’s usage-based licensing models provide flexibility for organizations with dynamic or cloud-based workloads. These options are particularly beneficial for cloud environments where resource demands fluctuate.

Key Usage-Based Licensing Models

• Pay-As-You-Go (PAYG):
  • Charges are based on actual resource consumption, offering cost-effectiveness for variable workloads.
• Annual Commitment:
  • Provides a discounted rate for organizations committing to a predetermined usage level over a year.
• Autonomous Database Licensing:
  • It requires one processor license or 25 Named User Plus licenses of Oracle Database Enterprise Edition for every 2 vCPU.

Key Considerations

• PAYG Flexibility:
  • Ideal for fluctuating workloads but may result in higher costs for stable, long-term deployments.
• Monitoring Usage:
  • Proper tracking of resource consumption is essential to optimize costs and avoid over-licensing.
• Cloud Suitability:
  • Usage-based licensing models are most effective in cloud environments or workloads with variable resource requirements.

Licensing for Oracle Exadata

Oracle Exadata offers specialized licensing models designed for its high-performance database platform. These models cater to varying organizational needs and workload patterns.

Key Licensing Models

• Capacity-Based Licensing:
  • Based on the total processing power of the Exadata system, measured in Oracle Compute Units (OCPUs) or processor cores.
  • Provides unlimited access to all Exadata features and capabilities.
  • Ideal for consistent, high-volume workloads.
• Feature-Based Licensing:
  • Enables organizations to license specific features or capabilities individually.
  • Offers flexibility but requires careful planning to avoid under-licensing or overpaying.
• Subscription-Based Licensing:
  • Follows a pay-as-you-go model with monthly or annual subscription options.
  • Lower upfront costs and scalability for evolving needs.
  • This may result in higher total costs over time compared to perpetual licenses.

Key Considerations

• Workload Patterns:
  • Choose a licensing model aligned with workload predictability and volume.
• Budget Constraints:
  • Evaluate long-term costs and consider negotiating multi-year agreements with capacity growth provisions.

Licensing for Oracle MySQL

Oracle MySQL provides flexible licensing options for organizations requiring a reliable and scalable database solution. These options are suitable for both open-source and proprietary deployment scenarios.

Key Licensing Options

• Open-Source GPL License:
  • Free to use, modify, and distribute.
  • Requires derivative works to be open-source under the GPL.
• Commercial License:
  • Designed for businesses needing proprietary solutions or additional support.
  • Allows organizations to keep their source code private.

MySQL Editions

• Classic Edition:
  • Available for embedded use only.
• Standard Edition:
  • Provides basic functionality for commercial use.
• Enterprise Edition:
  • It offers advanced features and support and costs $5,350 per server socket.

Key Considerations

• Commercial Licensing:
  • Obtained through Oracle partners using ASFU or ESL Distribution Agreements.
• Edition Selection:
  • Match the edition with deployment needs to avoid unnecessary costs.

Oracle Database Licensing in AWS

Oracle Database licensing on AWS accommodates both license-included and Bring Your Own License (BYOL) models, offering flexibility for organizations migrating to or operating in the cloud.

Key Licensing Models

• License Included (LI):
  • AWS provides the Oracle database license, eliminating the need for separate purchases.
  • Available for Oracle Standard Edition One and Two.
• Bring Your Own License (BYOL):
  • Allows organizations to use existing Oracle Database licenses on AWS RDS.
  • Required for editions other than Standard Edition One and Two.

Key Considerations

• Licensing Metrics:
  • Based on the number of virtual CPUs (vCPUs) on the EC2 instance.
• Cost Efficiency:
  • BYOL can reduce costs for Amazon RDS instances by leveraging existing investments.
• Enterprise Edition Requirements:
  • Oracle Database Enterprise Edition must use the BYOL model for deployment on Amazon RDS.

Oracle Database Licensing in Azure

Oracle Database licensing on Azure provides organizations flexible deployment options to integrate effectively with Microsoft’s cloud platform.

Key Licensing Options

• Bring Your Own License (BYOL):
  • Organizations can use existing Oracle Database licenses, including those under unlimited license agreements (ULAs).
  • Offers cost savings by leveraging current investments.
• License Included:
  • Organizations can purchase Oracle Database licenses bundled with Azure resources through the Azure marketplace.

Key Considerations

• Oracle Database@Azure:
  • This offering, which will launch in early 2025, initially in the EU and North America, will enable deeper integration between Oracle and Azure environments.
• Licensing Metrics:
  • Based on vCPU usage, two vCPUs are equivalent to one processor license.
• Azure’s Constrained vCPU Feature:
  • Helps reduce licensing requirements by limiting the number of active vCPUs in specific deployments.
• Cost Structure:
  • Customers are charged for the Oracle Database license, and the associated Azure compute and storage resources, which requires careful budgeting for cloud deployments.

Oracle Database Licensing FAQ

What are the main licensing models for Oracle Database?
Oracle offers Named User Plus (NUP) licensing for individual users or devices and processor-based licensing for environments with undefined user counts.

How is processor licensing calculated?
Processor licensing depends on the number of cores in the server, multiplied by a core factor from Oracle’s Core Factor table.

What is the minimum NUP license requirement?
Enterprise Edition requires at least 25 Named User Plus licenses per processor. Standard Edition 2 requires 10 NUP licenses per server.

Does Oracle allow VMware VM cores to be licensed?
No, for VMware environments from vSphere 5.1 onwards, all physical cores across all hosts in the same vCenter Server must be licensed.

Can I use my existing Oracle licenses in the cloud?
Oracle’s BYOL (Bring Your Own License) program allows you to apply on-premises licenses to cloud deployments like AWS, Azure, or Oracle Cloud.

What is Pay-As-You-Go (PAYG) licensing?
PAYG charges for Oracle database usage based on actual resource consumption, which is suitable for fluctuating workloads.

What are the limitations of SE2 licensing?
From version 19c onwards, Oracle SE2 supports up to two processor sockets, 16 CPU threads, and no Real Application Clusters (RAC).

How does Oracle license non-production environments?
Non-production environments, including development and testing, require the same full licensing as production deployments.

What is the cost of Oracle database processor licenses?
Processor licenses typically cost $17,500 per processor for Enterprise Edition, with additional costs for support and options.

What is the purpose of the Oracle Core Factor table?
The Core Factor table adjusts licensing requirements based on processor type. The common factor for x86 and AMD processors is 0.5.

What is Oracle’s Universal Cloud Credits program?
Universal Cloud Credits provide flexible access to Oracle Cloud services, allowing you to allocate credits across multiple workloads.

What licensing options are available for Oracle RAC?
Oracle RAC licenses are available as processor-based or NUP and must match the licensing metric used for Oracle Database Enterprise Edition.

Does Oracle offer specific licenses for testing environments?
Oracle does not offer separate licenses for testing. Full licenses are required, though testing failover environments may have temporary exceptions.

How do I manage Oracle licensing for Azure?
Azure supports BYOL and license-included options. Oracle Database@Azure will launch in 2025 and integrate Oracle databases with Azure’s infrastructure.

What are the penalties for non-compliance with Oracle licensing?
Non-compliance may result in backdated licensing fees, penalties, and the potential need to purchase additional licenses at list price.