Running Oracle Real Application Clusters (RAC) on AWS: Licensing
Oracle Real Application Clusters (RAC) provides high availability and scalability for Oracle databases by running multiple instances across several servers. While Oracle RAC is possible on AWS, implementing it requires additional steps and careful licensing considerations.
This article provides detailed insights into running Oracle RAC on AWS, clearly explaining licensing implications, technical challenges, and alternative options.
Read Oracle on AWS Licensing FAQs 2 of 4
1. Can You Run Oracle RAC on AWS?
Availability on AWS:
- AWS does not natively support Oracle RAC in any managed service (e.g., Amazon RDS).
- With custom or third-party clustering solutions, Oracle RAC can only run on AWS EC2 or VMware Cloud on AWS (VMC).
Typical Deployment Approaches:
- Third-party solutions such as FlashGrid or SIOS for cluster management.
- Custom configurations with EC2 instances and shared storage via third-party storage software or AWS storage services.
2. Licensing Oracle RAC on AWS
Running Oracle RAC significantly impacts Oracle database licensing. The key points to consider are:
Full Licensing per RAC Node:
- Each server node in the RAC cluster runs a full Oracle Database Enterprise Edition instance.
- You must license each node separately for:
- Oracle Database Enterprise Edition (EE) licenses.
- Oracle RAC option licenses.
License Calculation Example:
- Scenario: 2-node RAC cluster on AWS, each EC2 node has eight vCPUs (with hyper-threading enabled):
- Enterprise Edition Processor licenses per node:
- 8 vCPUs ÷ 2 = 4 EE licenses per node
- RAC Processor licenses per node (matching EE):
- 4 RAC licenses per node
- Enterprise Edition Processor licenses per node:
Summary Example:
- 2-node RAC cluster (8 vCPUs each node):
- 8 EE Processor licenses total (4 per node)
- 8 RAC Processor licenses total (4 per node)
No Reduction or Sharing:
- Each processor in the RAC cluster requires its own EE and RAC licenses.
- Licensing costs effectively double for a 2-node RAC compared to a single-instance database.
3. Oracle RAC and Standard Edition (SE2)
Important Limitations:
- Oracle Standard Edition 2 (SE2) does not support RAC.
- Historically, Oracle allowed limited RAC functionality on Standard Edition (pre-SE2), but this was discontinued.
- Today, RAC is exclusively available for Oracle Database Enterprise Edition.
AWS Implications:
- RAC on AWS requires Enterprise Edition licenses (no Standard Edition option).
- Amazon RDS does not support RAC for any Oracle edition, making EC2 or VMC your only options.
Read Common Pitfalls in Oracle Licensing on AWS.
4. Technical Challenges of Running RAC on AWS
Implementing Oracle RAC on AWS requires overcoming technical challenges, primarily involving shared storage and clustering software:
Lack of AWS Native Shared Storage:
- Oracle RAC requires shared storage for database files, something AWS EC2 does not natively provide.
- Solutions include:
- Third-party software solutions like FlashGrid or SIOS to replicate shared storage functionality.
- AWS Elastic File System (EFS) or FSx for ONTAP (though performance and Oracle certification may vary).
Support and Certification Concerns:
- Oracle typically does not officially certify RAC deployments on AWS.
- However, Oracle does provide support if you:
- Run a certified OS and database version.
- Demonstrate that issues are not caused by unsupported storage or clustering solutions.
- Oracle support may request issue reproduction on non-AWS infrastructure in complex scenarios.
Practical Example:
- Company XYZ deploys a 2-node RAC cluster on AWS EC2:
- Uses FlashGrid for storage and clustering.
- Oracle provides support if the OS (Oracle Linux, RHEL) and Oracle DB versions are certified.
5. Cost and Licensing: RAC vs. Alternative High Availability (HA) Solutions
Oracle RAC licensing can be significantly more expensive than alternative high-availability setups on AWS. Here’s how they compare:
Oracle RAC Licensing Costs:
- Requires Enterprise Edition and RAC licenses for every active node.
- No licensing grace period or passive-node exemption (each node is always fully licensed).
Alternatives with Lower Licensing Costs:
- Oracle Data Guard or Active Data Guard setups:
- Data Guard standby servers may be licensed differently:
- A fully passive standby (in recovery mode, used <10 days/year for testing or failovers) generally does not require additional licensing.
- Active Data Guard (open read-only standby) requires additional licensing but can be more affordable than RAC.
- Data Guard standby servers may be licensed differently:
- Amazon RDS Multi-AZ (non-RAC, managed HA):
- Included with AWS-managed infrastructure (no RAC license needed).
- Limited to single-instance databases, no active-active writes.
Example Scenario (Cost Comparison):
- Scenario 1 (RAC): 2-node RAC, each node eight vCPUs:
- 8 EE licenses + 8 RAC licenses
- Scenario 2 (Data Guard): 1 primary (8 vCPUs), one passive standby (idle, failover-only):
- 4 EE licenses (primary node only)
- Passive standby: If it is truly passive (unless actively used >10 days/year), no extra licensing is required.
Alternative HA configurations (Data Guard or AWS Multi-AZ) can offer substantial licensing cost savings compared to RAC.
6. Recommended Best Practices for Licensing Oracle RAC on AWS
Clearly understanding Oracle licensing is crucial if you decide to implement RAC on AWS:
- ✅ Always license each RAC node fully (Enterprise Edition and RAC licenses).
- ✅ Document your RAC licensing clearly for Oracle audit readiness.
- ✅ Consider cost-effective alternatives (Data Guard, Multi-AZ) unless an active-active configuration is strictly necessary.
- ✅ Ensure storage and clustering solutions used on AWS are Oracle-supported or documented for support scenarios.
Practical Licensing Summary: Oracle RAC on AWS
| Scenario | RAC Required? | EE Licenses | RAC Licenses | Licensing Cost |
|---|---|---|---|---|
| Single-instance (8 vCPUs) | ❌ No | 4 | 0 | Lowest |
| 2-node RAC cluster (8 vCPUs each node) | ✅ Yes | 8 (4 per node) | 8 (4 per node) | Highest |
| Data Guard (1 active + 1 passive standby, 8 vCPUs) | ❌ No | 4 (active only) | 0 (if passive) | Moderate |
| Active Data Guard (1 active + 1 open-read standby) | ❌ No | 8 total (4 per node) | 4 Active Data Guard licenses | Moderate-high |
Common Misunderstandings Corrected
- Misconception: “AWS provides Oracle RAC as a managed service.”
- Reality: RAC requires manual or third-party implementations; AWS RDS does not support RAC.
- Misconception: “Passive RAC nodes don’t require licenses.”
- Reality: All RAC nodes must be fully licensed—no passive-node exemption.
- Misconception: “Standard Edition supports RAC on AWS.”
- Reality: SE2 discontinued RAC support—Enterprise Edition required.
Read How to License Oracle Database Options (RAC, Multitenant, Partitioning) on AWS..
Conclusion: Oracle RAC on AWS – Licensing and Deployment Insights
Running Oracle RAC on AWS is technically feasible but involves complexities and higher licensing costs than other high-availability solutions like Oracle Data Guard or AWS Multi-AZ.
Key Points to Remember:
- RAC on AWS requires third-party clustering software or custom configurations.
- Licensing each RAC node fully (EE and RAC option) significantly increases costs.
- Alternative HA solutions often provide comparable availability at lower licensing expenses.
Careful consideration of RAC’s licensing implications, technical challenges, and possible alternatives ensures that your Oracle database deployment on AWS effectively aligns with business and budget requirements.
