Oracle RAC One Node licensing is one of the quietest sources of database back-license exposure in the enterprise, because the trap is not the active database — it is the passive node sitting beside it. Buyers license the server the database runs on and forget that Oracle counts every node where the software is installed. This guide explains exactly what RAC and RAC One Node cost, when the license applies, the narrow 10-day failover exception, and how to defend an inflated LMS claim.
Short answer: Oracle RAC One Node is a separately licensed Enterprise Edition option, priced at roughly $10,000 per processor, that runs a single database on one cluster node at a time with the ability to relocate or fail over to another node. Every node in the cluster — active and passive — must be fully licensed, except for one spare node under the strict 10-day failover rule.
Oracle RAC One Node is a single-instance variant of Oracle Real Application Clusters that runs one active database instance on one node of a cluster, while retaining the ability to relocate that instance to another node — either planned, using online relocation, or unplanned, as automatic failover. It delivers cluster-grade availability and rolling-patch capability without the cost and complexity of running the database active-active across every node.
It sits between two extremes. A single-instance database on one server has no built-in node-level failover. Full Oracle RAC runs the same database concurrently on multiple nodes for both availability and scale-out performance. RAC One Node gives you the failover protection of a cluster while licensing a cheaper option — but it is still a paid Enterprise Edition option, and the licensing rules that catch buyers are identical to full RAC.
The structural trap: RAC One Node is sold and understood as a "single node" product. That framing leads buyers to license a single server. But the option only has value because a second node exists to relocate to — and Oracle requires that second node to be licensed for both Enterprise Edition and the RAC option from the day the software is installed on it.
Short answer: Full RAC runs one database active-active across multiple nodes at once, for both availability and scalability. RAC One Node runs the database on a single node at a time and relocates it to another node when needed. Both are separately licensed EE options; RAC One Node is roughly 43% of the per-processor cost of full RAC.
The practical distinction is concurrency. With full RAC, all licensed nodes service connections simultaneously through Single Client Access Name (SCAN) and services, sharing one database via Cache Fusion. With RAC One Node, only one instance is open against the database at any moment; the other node is a warm target for relocation. RAC One Node also includes Online Database Relocation, which lets a DBA move the running instance to another node with no outage during patching or maintenance.
Crucially, the conversion path runs one way and runs easily. A RAC One Node database can be promoted to full multi-node RAC online with a single srvctl convert database command and no data migration. This is convenient technically and dangerous commercially: estates routinely convert to full RAC for scalability without raising a purchase order for the more expensive option. See our Oracle database options licensing guide for how this pattern repeats across the option portfolio.
Oracle RAC One Node is priced per processor at approximately $10,000 per processor list, compared with approximately $23,000 per processor for full RAC. Both options are additive to the Oracle Database Enterprise Edition base license of approximately $47,500 per processor. Processor counts are derived from the Oracle Core Factor Table: physical cores multiplied by the architecture's core factor, typically 0.5 for x86, rounded up.
| Component | Per Processor List | Two-Node Cluster (16 procs total) |
|---|---|---|
| Enterprise Edition base | $47,500 | $760,000 |
| RAC One Node option | $10,000 | $160,000 |
| Full RAC option (for comparison) | $23,000 | $368,000 |
| EE + RAC One Node total | $57,500 | $920,000 |
The table assumes each 16-core server counts as 8 processors after the 0.5 core factor, and two nodes are licensed because both must be. Add the standard 22% annual support to every line. Negotiated discounts of 40–60% off list are achievable on net-new option purchases, but few enterprises proactively license the spare node — which is why so many RAC settlements arrive as back-license claims at or near list, compounded by support arrears. Our Oracle license optimization service models the EE-plus-option stack before any purchase commitment.
Short answer: Yes. Oracle's policy is that every node where Oracle Database software is installed and/or running in a cluster must be fully licensed for Enterprise Edition and the RAC One Node option — including the node the instance is not normally running on. Installation, not active use, triggers the requirement. The only relief is the 10-day failover rule.
This is the single most expensive misunderstanding in RAC licensing. Buyers reason that because RAC One Node runs on one node at a time, they only owe a license for "the node it runs on." Oracle's position, set out in its licensing policy documents, is that a program is "installed and/or running" on every cluster node that has the binaries and is configured to host the instance. A warm standby node that could take over at any moment is, by definition, configured to host it.
The exposure compounds when the failover target also hosts standby copies. An Active Data Guard standby node carrying a RAC One Node database needs Enterprise Edition, RAC One Node, and Active Data Guard licenses on its processors. We routinely find estates that licensed the primary cluster correctly and left the disaster-recovery node entirely unlicensed — see our broader guidance on Oracle dual-use and failover rights.
The 10-day failover rule is the one narrow exception that lets a node run Oracle unlicensed. Oracle's policy permits a single spare node in a failover cluster — one that shares storage with the licensed nodes — to run an Oracle program for up to a total of ten separate 24-hour periods in any calendar year, when a licensed node fails. The intent is to cover genuine unplanned outages, not to subsidise routine workload.
The conditions are unforgiving and are exactly where LMS attacks:
In practice the 10-day rule rarely rescues a RAC One Node deployment, because the second node is configured as a permanent relocation target rather than a rarely-used spare. Treat it as a safety net for true outages, not as a licensing strategy.
Our forensic compliance review maps every node, instance, and standby in your cluster and calculates exact RAC exposure — before Oracle's LMS team does. Former Oracle insiders, 100% buyer-side.
Not anymore. For Oracle Database 18c and earlier, Standard Edition 2 included RAC at no additional option cost, within SE2's hard limit of two sockets per cluster. Starting with Oracle Database 19c, Oracle removed RAC support from SE2 entirely. SE2 databases on 19c and later — the current long-term-support release — cannot be clustered with RAC at all.
This change quietly forces an architectural decision during upgrades. Organisations that ran SE2 RAC for cheap availability on 18c face three options at 19c: move to single-instance SE2 with a different high-availability approach, migrate to Enterprise Edition and license the RAC or RAC One Node option, or move the workload elsewhere. Our Enterprise Edition licensing guide and the Oracle database licensing guide cover the cost step-up in detail, because the jump from "free SE2 RAC" to "EE plus a paid RAC option" is one of the larger surprise costs in a 19c upgrade programme.
Oracle's License Management Services (LMS) team detects RAC usage with near certainty, because the database records it in multiple places. The primary signals are the V$OPTION view, which reports whether Real Application Clusters is installed, and DBA_FEATURE_USAGE_STATISTICS, which logs whether RAC or RAC One Node features have actually been exercised and when. The cluster topology itself is visible through Oracle Clusterware configuration and the GV$ global views.
-- Is the RAC option installed? SELECT parameter, value FROM v$option WHERE parameter = 'Real Application Clusters'; -- Has RAC / RAC One Node been used, and when? SELECT name, detected_usages, first_usage_date, last_usage_date FROM dba_feature_usage_statistics WHERE name LIKE '%RAC%' OR name LIKE '%One Node%'; -- How many instances/nodes service this database? SELECT inst_id, instance_name, host_name, status FROM gv$instance;
Because gv$instance and the Clusterware inventory enumerate every configured node, an auditor can immediately see whether your purchased license count matches the number of nodes in the cluster. A two-node RAC One Node cluster with only one node's worth of EE and option licenses is flagged in the first pass. For the broader script catalogue, see our guide to Oracle LMS audit scripts.
RAC and RAC One Node claims are frequently larger than the customer actually owes, and several challenge vectors reliably reduce them. The work is to separate genuine exposure from measurement error before any number is conceded.
Processor count and core factor. LMS overclaims regularly arise from counting hyperthreads as cores, applying the wrong core factor, or including powered-off or decommissioned nodes. A forensic re-measurement against the Core Factor Table commonly cuts the processor base before the option is even discussed.
RAC One Node versus full RAC. If DBA_FEATURE_USAGE_STATISTICS shows only RAC One Node feature usage, the claim should be priced at the RAC One Node rate, not the full RAC rate. Oracle sometimes defaults to the more expensive option; the usage history is your evidence.
The 10-day rule. Where a node genuinely operated only as an unplanned failover target within the ten-day allowance, that usage is licensed under policy and should be excluded from the claim entirely.
First-usage date. Back-license periods are calculated from first detected usage. Data Pump imports and database clones do not preserve original timestamps, so a recent first_usage_date may not reflect a long history — and equally cannot be assumed to. Establishing the true date narrows the arrears window. Our Oracle audit defense service has reduced database-option claims substantially using exactly these methods; one engagement, documented in our case studies, closed a multi-million-dollar options claim for a fraction of the opening demand. Before submitting any script output to Oracle, read our note on Oracle audit data disclosure.
Do not self-report without advice. Running Oracle's measurement scripts and returning the raw output typically confirms the maximum possible exposure, including unlicensed passive nodes you might otherwise remediate first. Engage independent advisers before any data leaves your organisation.
Full RAC runs a single database active-active across multiple nodes at the same time, for both availability and scalability. RAC One Node runs the database on one node at a time and can relocate or fail it over to another node. Both are separately licensed Enterprise Edition options, and both require every node in the cluster to be fully licensed.
RAC One Node lists at roughly $10,000 per processor, versus about $23,000 per processor for full RAC, added on top of the ~$47,500 Enterprise Edition base license. Processors are counted with Oracle's Core Factor Table, so a 32-core two-socket Intel server counts as 16 processors before pricing the option.
Yes. Every node with Oracle software installed and configured in the cluster must be fully licensed for Enterprise Edition and the RAC One Node option, including the passive node. The only exception is the 10-day failover rule, which allows unlicensed failover to one spare node for up to ten separate days per calendar year.
It allows one unlicensed spare node in a failover cluster, sharing the same storage, to run an Oracle program for up to a total of ten separate 24-hour periods per calendar year when a licensed node fails. Any usage beyond ten days, a second simultaneous failover node, or planned relocation requires full licensing. Any part of a day counts as a full day.
No longer. Oracle removed RAC support from Standard Edition 2 starting with Oracle Database 19c, so SE2 on 19c and later cannot run RAC. On 18c and earlier, SE2 included RAC within the two-socket limit, but those releases are out of Premier Support.
Yes, online, with a single srvctl command and no data migration. This convenience is a common cause of under-licensing: estates convert to full RAC for scalability without buying the more expensive option, which costs roughly 2.3 times RAC One Node per processor.
The complete guide to Oracle Database options, metrics, and compliance traps — written by former Oracle insiders for enterprise IT and procurement teams.
Weekly briefing on Oracle audit tactics, license changes, and negotiation intelligence — read by 2,000+ Oracle stakeholders at Fortune 500 enterprises.
Independent. Buyer-side. Not affiliated with Oracle Corporation.
Oracle's LMS team counts every node. A forensic compliance review maps your cluster, validates the option in use, and gives you the evidence base to license correctly or defend a claim — on your terms.
Not affiliated with Oracle Corporation. 100% independent, buyer-side advisory.