Oracle licensing

Oracle RAC Licensing

Oracle RAC Licensing Overview

  • Add-on for Enterprise Edition only.
  • Two primary models: Processor and Named User Plus.
  • Processor cost: $23,000 per processor.
  • Requires licensing of all cluster nodes.
  • Compliance with Oracle Core Factor Table.

Oracle RAC Licensing: A Comprehensive Guide

Oracle RAC Licensing A Comprehensive Guide

Oracle Real Application Clusters (RAC) offers a powerful way to scale and provide high availability for Oracle Databases by allowing multiple instances to run on different servers. RAC enhances database reliability and performance, which is crucial for large enterprises with demanding workloads.

However, Oracle RAC licensing is known for being complex, and understanding the licensing models is vital to avoiding compliance pitfalls and managing costs effectively.

This guide provides a detailed overview of Oracle RAC licensing requirements, primary licensing models, cost calculations, cloud environment considerations, disaster recovery licensing, and compliance rules.

Core Licensing Requirements

Oracle RAC is exclusively available as an add-on license for Oracle Database Enterprise Edition (DB EE). Your underlying database must be licensed under Enterprise Edition to use RAC.

The licensing metric used for RAC must match the license type of the underlying Oracle Database EE. Understanding this requirement is critical for businesses deploying RAC, as licensing inconsistencies can lead to significant compliance issues.

The licensing requirements for RAC are straightforward but restrictive:

  • Enterprise Edition Only: RAC is not available for Oracle Database Standard Edition, so organizations must invest in Enterprise Edition before adding RAC.
  • Matching Metrics: The licensing metric for RAC must align with the licensing metric of the underlying Oracle Database EE—whether it’s based on processors or Named User Plus (NUP). This consistency is essential to ensure compliance.

Primary Licensing Models

Oracle RAC can be licensed using two primary models—Processor-Based Licensing and Named User Plus (NUP). Each model’s pricing and requirements must be carefully considered before deployment.

Processor-Based Licensing

Processor-based licensing is commonly used in enterprise environments where counting individual users accessing the system is challenging.

Here are the key details:

  • Base Cost: $23,000 per processor, the standard licensing cost for each processor in the cluster.
  • All Processors Must Be Licensed: You must license all processors across every node of the RAC cluster. For example, if you have an 8-node cluster and each node has two processors, you need to license 16 processors.
  • Core Factor Table: Oracle uses the Core Factor Table to determine the number of processors that need to be licensed based on the type of hardware used. This helps account for the differences in processing power between different hardware models.

Cost Calculation Example (Processor-Based):

  • Cluster Size: 8 nodes, each with two processors.
  • Total Processors: 16 processors.
  • Total Licensing Cost: $23,000 per processor x 16 processors = $368,000.

Named User Plus (NUP)

The Named User Plus licensing model is used when the exact number of users accessing the database can be determined. This model is often more cost-effective for environments with fewer users.

  • Base Cost: $460 per named user.
  • Licensing Requirement: You must license all users with access to the database. This includes direct and indirect users, meaning even users accessing the database through middle-tier applications need to be counted.

Cost Calculation Example (Named User Plus):

  • Number of Users: 500 users accessing the RAC cluster.
  • Total Licensing Cost: $460 per user x 500 users = $230,000.

Cloud Environment Licensing

Deploying Oracle RAC in cloud environments adds another layer of complexity to licensing.

Unlike traditional on-premise deployments, RAC licensing in cloud environments has several specific considerations:

  • Not Eligible Under Oracle’s Cloud Policy: Oracle RAC is not automatically eligible under Oracle’s “Cloud Policy,” meaning that you cannot use Oracle’s Universal Cloud Credits to license RAC in the cloud.
  • Core-Based Licensing Still Applies: The traditional core-based licensing model must be used, and the Core Factor Table is still applicable for determining licensing requirements, even in cloud environments.
  • Limited Availability: Oracle RAC is available in cloud environments primarily through Oracle’s Dedicated Hosts or VMware Cloud solutions. Public shared clouds may not support RAC deployments, limiting your choices for cloud-based implementations.

Disaster Recovery Licensing

When configuring Oracle RAC for disaster recovery, there are unique licensing requirements that differ from a typical production setup:

  • Standby Servers: Oracle RAC does not need to be licensed on disaster recovery (DR) servers unless those servers are actively used to run database workloads. Standby servers in a passive mode—used solely for failover and testing—do not require full RAC licensing.
  • Production Metrics Apply: If the DR environment is activated and used for more than a brief period (e.g., for extended testing or live operations), the licensing metrics for RAC must match those of the production environment, ensuring consistency.

Standard Edition Restrictions

RAC was available for Standard Edition 2 (SE2) in previous Oracle versions. However, starting with Oracle 19c, this has changed:

  • No RAC for SE2: As of Oracle 19c, RAC is no longer supported in Standard Edition 2. Organizations that require RAC must upgrade to Enterprise Edition and then add RAC as an add-on.
  • Upgrade Considerations: For organizations running RAC on SE2, this change means upgrading to Enterprise Edition or exploring alternatives such as Oracle Data Guard for high availability and disaster recovery.

Compliance Requirements

Compliance is critical in Oracle licensing, and RAC is no exception. Several important rules must be adhered to to remain compliant:

  • Full Node Licensing: All nodes in an RAC cluster must be fully licensed. This includes both active and standby nodes within the RAC environment. There are no exceptions for inactive or occasionally used nodes.
  • Matching Metrics: The licensing metrics for Oracle RAC must always match those of the underlying Oracle Database EE. Using different metrics for RAC and the base database can lead to compliance issues during audits.
  • Audit Considerations: Oracle frequently audits its customers to ensure compliance, particularly with products like RAC that involve complex deployments. Non-compliance can result in significant penalties, and a lack of understanding of RAC licensing rules is one of the most common reasons for audit findings.

Cost Considerations for Oracle RAC Licensing

The cost of Oracle RAC can add up quickly, especially for larger deployments. To avoid surprises, it’s essential to consider all licensing aspects and plan accordingly.

Processor-Based Licensing

With processor-based licensing, businesses must ensure that all processors in the RAC cluster are properly licensed. Given the $23,000 per processor cost, this model is often preferred in larger environments where counting individual users is prohibitive. However, utilizing Oracle’s Core Factor Table is essential to determine the correct number of licenses based on the specific hardware.

Named User Plus Licensing

NUP licensing can be more economical in smaller environments. However, it must accurately count all users, including those indirectly accessing the database through middleware. Even though NUP might be more cost-effective at smaller scales, licensing errors—such as failing to count all users—can lead to non-compliance issues.

Cloud Deployment

Moving Oracle RAC to the cloud involves additional costs and complexity. Oracle’s policies regarding RAC on cloud platforms are quite strict, and customers must use traditional core-based licensing even when moving workloads to Oracle Cloud Infrastructure (OCI) or other cloud providers. Dedicated Hosts can be an option, but they are expensive due to the nature of the infrastructure.

Maximizing Value from Oracle RAC Licensing

Oracle RAC offers powerful capabilities for scaling Oracle Database environments and ensuring high availability. However, maximizing the value of RAC requires careful planning and diligent licensing management.

  • Choose the Right Licensing Model: Evaluate your current and future database workloads to choose the most appropriate licensing model. Processor-based licensing is often preferable for large, highly concurrent environments, whereas smaller environments may benefit from NUP licensing.
  • Monitor Usage Continuously: Review your database workloads and usage metrics regularly to determine if your current licensing model is still optimal. Changes in user numbers or infrastructure can impact your compliance status.
  • Cloud Strategy: If moving to the cloud, account for Oracle’s specific RAC licensing requirements. Look into options like Oracle’s Dedicated Hosts or VMware Cloud solutions that can support RAC. Remember that RAC is not generally supported in public cloud-shared environments.
  • Stay Updated on Policy Changes: Oracle licensing policies, especially for RAC, can change frequently. Staying informed about these changes helps avoid costly surprises, particularly if Oracle changes impact your compliance.

Frequently Asked Questions about Oracle RAC Licensing

What is Oracle RAC Licensing? Oracle RAC licensing is an add-on for Oracle Database Enterprise Edition that allows multiple database instances to run across different nodes, providing high availability and scalability.

Is Oracle RAC available for Standard Edition? No, Oracle RAC is only available for Enterprise Edition. Since Oracle 19c, RAC support has been discontinued for Standard Edition 2.

What are the primary licensing models for RAC? Oracle RAC can be licensed using either the Processor-based or Named User Plus (NUP) model, depending on the environment’s requirements.

How does Processor-based licensing work for RAC? In Processor-based licensing, all processors across every cluster node must be licensed. Oracle calculates costs using the Core Factor Table to adjust for different hardware types.

What is Named User Plus (NUP) licensing? NUP licensing is used when the number of users accessing the database is known. All users, including indirect users, must be licensed. This model can be more cost-effective in smaller environments.

How much does it cost to license Oracle RAC per processor? The base cost is $23,000 per processor, which applies to all cluster processors regardless of usage frequency.

Are Oracle RAC licenses required for disaster recovery nodes? RAC licenses are not required for passive disaster recovery nodes and are only used for failover purposes. However, licensing is necessary if they are actively used.

Can Oracle RAC be used in cloud environments? Yes, but Oracle RAC must be licensed traditionally, even in the cloud. Oracle’s Core Factor Table and standard core-based licensing models still apply.

Is RAC covered under Oracle’s Cloud Policy? No, Oracle RAC is not covered under Oracle’s Universal Cloud Policy. Licensing for RAC in cloud environments must follow traditional core-based guidelines.

What licensing considerations apply to Oracle RAC in VMware? In VMware, Oracle requires licensing for all processors in a virtual environment unless strict partitioning rules are met. If this policy is misunderstood, it can significantly increase licensing costs.

Do all nodes in an RAC cluster need to be licensed? Yes, all nodes in an Oracle RAC cluster must be fully licensed, even if some are only used occasionally. This ensures compliance during audits.

How is licensing affected by infrastructure changes? If infrastructure changes, such as adding new nodes, Oracle RAC licenses must be updated to reflect all new processors or users involved, depending on the licensing model used.

What happens if there is a licensing mismatch between RAC and the database? A mismatch between Oracle RAC licensing and the underlying Database Enterprise Edition licensing can result in non-compliance and significant audit risks and financial penalties.

How do experts help with Oracle RAC licensing compliance? Oracle license experts help organizations understand and apply Oracle’s licensing rules, conduct internal audits, manage infrastructure changes, and prepare for Oracle’s official audits to avoid non-compliance.

Why is Oracle RAC licensing considered complex? It is complex due to the strict rules regarding node licensing, cloud deployments, metrics alignment, and frequent policy updates. Missteps can lead to high costs and compliance risks.

Author

  • Fredrik Filipsson

    Fredrik Filipsson brings two decades of Oracle license management experience, including a nine-year tenure at Oracle and 11 years in Oracle license consulting. His expertise extends across leading IT corporations like IBM, enriching his profile with a broad spectrum of software and cloud projects. Filipsson's proficiency encompasses IBM, SAP, Microsoft, and Salesforce platforms, alongside significant involvement in Microsoft Copilot and AI initiatives, improving organizational efficiency.

    View all posts