Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.

500+ enterprise clients · Est. 2016 · 15-min response · No commitment

Get Free Oracle Analysis →

What Is Oracle RAC One Node?

Oracle Real Application Clusters One Node (RAC One Node) is a single-instance, Oracle-managed HA option that runs one active database instance on a single node, with an automated failover capability that can migrate the instance to a second node within minutes. Oracle positions it as a cost-effective step between standalone Database Enterprise Edition and full multi-node RAC — lower availability commitment than RAC, higher than single-instance.

In practice, RAC One Node requires the RAC One Node option licence on every processor on both the primary and standby nodes, not just the active node. Oracle's licensing rules treat the standby node as a licensed entity the moment it is available for failover — even when it is idle. For most two-node deployments this means you are paying for four processors worth of RAC One Node option, not two.

RAC One Node vs. Full RAC: The Licensing Distinction

The critical distinction between RAC One Node and full RAC is operational scope. Full RAC permits multiple simultaneous active instances across all licensed nodes — the entire cluster must be licensed for Database EE, the RAC option, and any additional options deployed. RAC One Node restricts you to a single active instance, but Oracle's rule that all nodes capable of running the database must be licensed still applies.

The practical consequence: a 2-node RAC One Node cluster with 16-core Intel processors (0.5 core factor) carries the same 16-processor licence count and the same RAC One Node option bill as a 2-node full RAC cluster with identical hardware. The £18,502 RAC One Node option cost applies to all 16 processors across both nodes.

The Full Cost Structure

Oracle's Processor licence list prices as of 2026 for a typical RAC One Node deployment stack as follows. These figures use Oracle's published UK list prices; actual invoiced prices after negotiation vary, but rarely fall below 60% of list for organisations without significant volume leverage.

Licence Component List Price (proc/yr) SnS Rate Annual SnS Cost
Database Enterprise Edition£37,50022%£8,250/proc
RAC One Node Option£84,10022%£18,502/proc
Active Data Guard (optional)£84,10022%£18,502/proc
Diagnostic Pack (auto-enabled)£33,70022%£7,414/proc
Tuning Pack (optional)£33,70022%£7,414/proc
Base DB EE + RAC One Node£26,752/proc

The Diagnostic Pack Auto-Activation Trap

Oracle Enterprise Manager's Performance Hub and SQL Monitoring features — both enabled by default in many DBAs' tooling — require Diagnostic Pack licence. Oracle LMS scripts detect usage automatically. On a 16-processor RAC One Node deployment, undiscovered Diagnostic Pack usage adds £118,624/yr to your annual support bill. This is the most common unexpected cost in LMS audits targeting RAC environments.

TPS Cost Model — Four Deployment Profiles

The following table models total annual Oracle support (SnS at 22% of net licence value) versus GoVendorFree third-party support (TPS) for a RAC One Node deployment across four common organisation sizes. All figures use base DB EE + RAC One Node option only; Diagnostic Pack, Tuning Pack, and Active Data Guard are excluded to show a conservative baseline.

Profile Hardware Processor Count Oracle SnS/yr TPS/yr Annual Saving
Mid-market single cluster 2-node, 2×8-core Intel (0.5) 8 processors £214,016 £79,186 £134,830 (63%)
Regional enterprise 2-node, 2×16-core Intel (0.5) 16 processors £428,032 £154,492 £273,540 (64%)
Multi-cluster enterprise 4×16-core across 3 clusters (0.5) 48 processors £1,284,096 £449,434 £834,662 (65%)
Large enterprise / SPARC 2-node SPARC T8-2 (1.0 factor) 64 processors £1,712,128 £599,245 £1,112,883 (65%)

These are headline figures on base licence only. Organisations with Diagnostic Pack, Active Data Guard, or Tuning Pack on the same nodes will see proportionally larger absolute savings — each additional option increases the SnS base by 22% of its own list price, which TPS eliminates entirely.

What Third-Party Support Covers

A common objection to Oracle third-party support for RAC One Node environments is that HA-specific issues — node failover failures, Clusterware events, SCAN listener instability — require Oracle to diagnose. This overstates Oracle SnS's responsiveness and understates what TPS delivers.

GoVendorFree TPS for Oracle RAC One Node environments covers:

What TPS Does Not Cover

Third-party support does not provide access to Oracle's new feature development pipeline, Oracle Cloud roadmap integration, or net-new product licences. Organisations actively planning a move to Oracle Autonomous Database or Oracle 23ai features will need to weigh TPS against their strategic cloud timeline. For organisations running stable 12c R2 through 19c environments with no Oracle Cloud dependency, this limitation is typically irrelevant.

The Virtualisation Licensing Trap

The single most common cost surprise for RAC One Node customers — and the issue most frequently exploited by Oracle LMS audits — is virtualisation. Oracle's processor counting rules for RAC are unambiguous: all physical processors on all nodes in the cluster must be licensed, regardless of virtualisation layer, VM allocation, or actual usage.

This means:

For a typical 4-host vSphere cluster running a 2-node RAC One Node deployment, the exposure is not 2×16 cores but 4×16 cores — doubling the processor count and the entire RAC One Node option bill. Under TPS, processor counting methodology is irrelevant — you pay for support of the software you actually run, not the hardware you theoretically could run it on.

For more on Oracle's LMS audit methodology and how to defend your position, see the Oracle LMS Audit Defence Playbook.

How Much Is Your RAC One Node Costing You?

Our engineers will map your RAC One Node environment, calculate your actual processor count under Oracle's rules, and deliver a precise TPS saving estimate — typically within 48 hours.

Get Your Cost Assessment Download Audit Playbook

Transition Process for RAC One Node Environments

Transitioning a RAC One Node environment to TPS follows a structured process that protects HA continuity throughout. The process typically completes in 30–45 days from contract signature.

Step 1 — Environment documentation: Full capture of RAC One Node configuration — node count, CPU type and core factor, Oracle Database version and patch level, Grid Infrastructure version, storage configuration, and any options deployed (Diagnostic Pack, ADG, Partitioning).

Step 2 — LMS audit risk assessment: Before terminating Oracle SnS, an assessment of open audit risk and any potential retroactive LMS exposure. Organisations with uncertified virtualisation configurations should complete remediation or scope containment before notifying Oracle of SnS termination.

Step 3 — Oracle SnS termination notice: Oracle requires 30 days' written notice to terminate support. TPS contract should be signed before notice is served to ensure no gap in coverage.

Step 4 — Knowledge transfer: GoVendorFree engineers conduct a full environment review, access relevant patch history, and document any known stability issues or recurring incidents to enable informed support from day one.

Step 5 — Go-live and SLA activation: 15-minute response SLA activates from the SnS termination date. All historical support context is transferred to the TPS team.

Industry Angles

Financial Services: RAC One Node is the dominant Oracle HA configuration for mid-tier banking applications — branch transaction processing, reporting databases, and FATCA/MiFID II data stores that require failover but not the full cluster resilience of multi-node RAC. The processor licensing exposure on virtualised vSphere environments in FS is typically 2–3× what IT believes they have licensed. TPS eliminates the ongoing LMS audit liability while maintaining the HA architecture.

Manufacturing / ERP: JD Edwards, Oracle EBS, and SAP Oracle database tiers frequently run on RAC One Node for manufacturing execution continuity. S/4HANA migration timelines for Oracle EBS customers typically stretch 3–5 years, making TPS cost reduction on the Oracle tier a high-value, low-risk decision during the migration period.

Healthcare: NHS Trust and private hospital groups running Oracle clinical applications on RAC One Node face two pressures simultaneously — constrained budgets and regulatory requirements for HA. TPS satisfies both: lower cost, maintained HA, and security patch backporting to satisfy CQC/DSPT obligations without version upgrades.

RAC One Node sits within a broader Oracle licensing and support landscape. The following resources provide complementary analysis: