Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle Real Application Clusters (RAC) is Oracle's flagship high-availability database architecture, deployed by the majority of large-scale Oracle Database customers in financial services, manufacturing, energy, and public sector. It is also Oracle's most aggressively priced database option — and the product whose support costs generate the most client demand for independent alternatives.
What Is Oracle RAC and Why Does It Cost So Much?
Oracle Real Application Clusters allows multiple servers (nodes) to run Oracle Database simultaneously, accessing a shared storage system. This provides both high availability — if one node fails, others continue operating — and horizontal scalability, as workloads can be distributed across nodes. RAC is widely used for mission-critical OLTP systems: banking transaction processing, insurance claims systems, manufacturing ERP, and utility billing platforms.
The cost problem is structural. Oracle RAC requires: (1) Oracle Database Enterprise Edition licences on all processors across all cluster nodes; (2) the Oracle Real Application Clusters option licence on all processors; (3) typically Oracle Active Data Guard for disaster recovery; and (4) optionally, Oracle Partitioning, Advanced Compression, and Diagnostic/Tuning Packs that are often activated by default. Each of these is separately licensed at per-processor pricing.
The Oracle RAC Processor Counting Trap
Oracle's licensing rule for RAC requires that all active processors in the cluster be licensed — not just the processors used by Oracle workloads. For a 4-node cluster with 16 cores per node: that is 64 processors × Oracle Core Factor (typically 0.5 for Intel x86, 1.0 for older RISC) = 32–64 Oracle Processor licences for base EE alone, before the RAC option is applied.
In virtualised environments, Oracle's position — that all physical processors in a cluster must be licensed regardless of VM placement — can multiply this further. A VMware cluster with 8 hosts, each with 24 cores, used to run two 4-node RAC clusters, would require all 192 cores to be licensed under Oracle's Soft Partition interpretation.
Running Oracle RAC on VMware is Oracle's most powerful audit leverage point. Oracle's LMS team claims licensing of all physical processors in the VMware cluster — typically 3–8× more processors than the RAC deployment actually uses. Combined with RAC option pricing at £18,500/processor/year, a single LMS audit finding can produce a multi-million-pound claim from a deployment that appears modest in scope.
Oracle RAC Full Licensing Cost Breakdown (2026)
| Licence Component | Oracle List Price (per processor) | Annual Support (22%) | Notes |
|---|---|---|---|
| Oracle Database Enterprise Edition | £37,500 | £8,250 | Required base for RAC |
| Real Application Clusters Option | £84,100 | £18,502 | Per processor on all nodes |
| Active Data Guard | £84,100 | £18,502 | DR standby (read-only access) |
| Partitioning Option | £52,600 | £11,572 | Common in OLTP/ERP environments |
| Diagnostic Pack | £33,700 | £7,414 | Often auto-activated via OEM |
| Tuning Pack | £33,700 | £7,414 | Often auto-activated via OEM |
For a typical 4-node RAC cluster (16 processors licensed after core factor): base support cost = 16 × (£8,250 DB EE + £18,502 RAC option) = £427,232/year. Adding ADG (if deployed), Partitioning, Diagnostic/Tuning Packs on all processors pushes the annual Oracle support bill for a single 4-node RAC cluster to £800K–£1.2M.
What Would Third-Party Support Cost for Your RAC Environment?
Share your RAC cluster configuration and we'll produce an independent cost comparison in 24 hours — covering TPS pricing, Oracle support equivalent, and projected 5-year TCO. No obligation.
Get Your RAC Cost Analysis →Third-Party Support Coverage for Oracle RAC
Third-party support covers the full Oracle RAC stack — including all the option and pack components that Oracle prices separately. Coverage scope includes:
- Oracle Database EE: Versions 10g R2 through 23c, all patch sets and PSUs
- RAC infrastructure: Clusterware / Grid Infrastructure (9i CRS through 23c), ASM, SCAN, GNS, VIP configuration
- RAC-specific components: Cache Fusion, GCS, GES, interconnect tuning, node eviction diagnosis, split-brain scenarios
- Oracle Active Data Guard / Data Guard: Redo log transport, apply lag management, role transition support
- Oracle Partitioning, Compression, and other Options: Full support for all option functionality in licensed versions
- OEM Diagnostic and Tuning Pack functionality: TPS provides equivalent performance monitoring, AWR analysis, and query optimisation without Oracle's management pack licences
Oracle RAC TPS Cost Model (4 Deployment Profiles)
| Deployment | Processors Licensed | Oracle Annual Support | TPS Annual Cost | Annual Saving |
|---|---|---|---|---|
| 2-node RAC, DB EE + RAC | 8 processors | £213,616 | £74,766 | £138,850 (65%) |
| 4-node RAC, DB EE + RAC + ADG | 16 processors | £746,048 | £261,117 | £484,931 (65%) |
| 8-node RAC, full options stack | 32 processors | £1,842,560 | £644,896 | £1,197,664 (65%) |
| Large cluster, 4-site RAC + DR | 64 processors | £3,685,120 | £1,289,792 | £2,395,328 (65%) |
Third-party support covers your existing RAC deployment exactly as it runs today. No architecture changes, no version upgrades, no database migrations, and no licence buybacks are required. You continue operating Oracle RAC with full technical support coverage — you simply stop paying Oracle's annual maintenance fees.
RAC TPS Transition: 5-Step Process
Transitioning a RAC environment to third-party support follows the same process as any Oracle Database support transition, with additional steps specific to RAC's clustered architecture.
- Current state documentation (2 weeks): Full inventory of all RAC nodes, Grid Infrastructure version, ASM diskgroups, ADG configuration, OEM management pack usage, and open Oracle SR status. This baseline protects against any Oracle claim that support was used beyond the termination date.
- TPS provider selection and contract (2 weeks): TPS agreement signed, SLA confirmed, support team briefed on RAC cluster topology and critical applications. Establish secure remote access channel for TPS support team.
- Open SR resolution (2–4 weeks): Resolve or transfer ownership of any open Oracle Support Requests before termination. Critical SRs involving active data issues should be resolved before the transition date.
- Oracle support termination notice (30 days): Written notice submitted to Oracle per contract terms. Oracle will typically attempt to retain the account — standard protocol is to acknowledge receipt without re-engaging Oracle on pricing.
- TPS go-live and knowledge transfer (1 week): Final knowledge transfer session with TPS engineering team. Establish runbook for escalation procedures, emergency contact protocol for P1 RAC incidents (node eviction, interconnect failure, ASM disk group dismount).
Sector Angles: Who Operates Oracle RAC and Why
💳 Financial Services
Core banking and payment processing. RAC is the dominant HA architecture for Oracle-based clearing, settlement, and trading systems. Regulatory uptime requirements (99.99%+) make RAC decommission difficult — TPS maintains coverage without architecture change.
⚡ Energy & Utilities
Billing and metering platforms. Large utilities (1M+ accounts) typically run Oracle RAC for billing engine HA. SAP IS-U / Oracle combinations are common — both often supported via TPS simultaneously.
🏭 Manufacturing & Automotive
Oracle EBS and JD Edwards on RAC. Production scheduling and materials management systems require 24/7 availability. TPS covers both the RAC infrastructure and the Oracle Applications layer simultaneously.
Oracle RAC and LMS Audit Risk
Oracle RAC environments are disproportionately represented in Oracle LMS audit targets for two reasons: the per-processor value of a RAC compliance claim is higher than any other Oracle product (RAC option + ADG + base EE = £44K+/processor/year combined support), and RAC deployments in virtualised environments present the most contested processor-counting scenarios in Oracle's audit playbook.
Organisations that exit Oracle support via TPS before an LMS audit notice is issued remove Oracle's primary audit leverage. The audit rights in Oracle's standard licence agreement are tied to the support relationship; independent analysis suggests that post-termination audit claims are significantly more difficult for Oracle to pursue. This is not a guaranteed protection — organisations should take independent legal advice — but it is one of the strategic considerations behind timing TPS transitions ahead of anticipated audit activity.
For organisations already under Oracle LMS audit with RAC in scope, our Oracle Audit Defence Playbook covers the specific RAC processor counting challenges and VMware virtualisation arguments in detail.