Oracle Disaster Recovery Licensing: The 10-Day Rule, Data Guard and DR Compliance

Why Oracle DR Licensing Is So Frequently Misunderstood

Oracle's disaster recovery licensing rules create licence exposure equal to or greater than the primary production environment. The 10-day rule — the most frequently misapplied exemption — has three conditions most DR architectures fail to meet: same data centre, shared physical storage, and a passive-only standby. When any one condition fails, the standby requires full licence coverage from the first day of each calendar year.es licence obligations — often at full production cost. Oracle's policies around DR, failover, and standby databases are deliberately complex, and the consequences of misreading them can result in significant audit claims.

The confusion starts with a genuine policy nuance: Oracle does offer a limited failover exemption. But the conditions under which that exemption applies are narrow, the threshold at which it expires is low, and the most common DR architectures that organisations actually build — active-passive with Data Guard, warm standbys, and geographically distributed clusters — fall well outside the exemption's scope in most cases.

The 10-Day Rule: What It Actually Says

Oracle's official data recovery licensing policy document specifies that in a clustered high-availability environment where multiple nodes share a single storage array, one node may run Oracle Database without a separate licence for up to a cumulative total of 10 calendar days per year. This is the "10-day rule."

The conditions are specific. The environment must be a clustered configuration with shared storage. The 10-day limit is cumulative across the calendar year — not per incident. Oracle always counts in calendar days: if the failover node is activated for 90 minutes, that still counts as a full day. The exemption applies to a single failover node per primary — you cannot rotate multiple unlicensed standbys and claim each one separately. And the exemption only applies to passive failover; the standby must not serve any queries or workloads while the primary is running.

If the failover runs for more than 10 cumulative days in a calendar year, or if the standby node actively serves any workload concurrently with the primary, the exemption is void and the node must be fully licensed for the entire period.

Standby Database Types and Their Licensing Obligations

Oracle recognises several categories of standby configuration, and each carries a different licensing outcome.

Cold Standby

A cold standby is a database server that is completely offline and not running Oracle software until a disaster is declared and a manual failover is executed. Oracle's policy does not require a separate licence for a purely cold standby — the software is installed but not running or applying any logs. However, as soon as failover is initiated and the standby begins running Oracle processes, the 10-day clock starts. If the standby is activated for a planned failover test that lasts 3 days, those 3 days consume your annual 10-day allowance.

Warm Standby (Passive Log Apply)

A warm standby is a database server that runs continuously in recovery mode, applying redo log shipments from the primary to keep the standby synchronised. Even though the standby is not serving user queries, Oracle's position is that the software is running — and therefore must be licensed. A warm standby in passive log-apply mode requires the same processor licences as the primary. This is one of the most significant and most often overlooked licensing obligations in Oracle DR architectures.

Active Standby (Active Data Guard)

An active standby opens the database in read-only mode while simultaneously applying redo logs from the primary, typically used to offload reporting or analytics workloads. This configuration requires Oracle Active Data Guard, which is a separately licensed database option. At Oracle's list price, Active Data Guard costs approximately $11,500 per processor. For a standby server with 32 cores (16 processor licences at the 0.5 Intel core factor), the Active Data Guard option alone adds approximately $184,000 to the licence cost — plus the base Database Enterprise Edition licensing, plus 22% annual support increasing at 8% per year.

Oracle Data Guard: Free Software, Expensive Implications

Oracle Data Guard is included with Oracle Database Enterprise Edition at no additional licence cost. The Data Guard software itself — the log shipping and synchronisation mechanism — does not require a separate licence. What requires licensing is the environment in which Data Guard operates. Specifically:

• The primary database must be fully licensed on all required processors.
• Any standby database that runs continuously (warm or active) must also be fully licensed on all its processors, at the same edition as the primary.
• Options licensed on the primary (such as Partitioning, Diagnostics Pack, or Tuning Pack) must also be licensed on the standby if those options are used or if their use on the primary implies use on the standby.
• Active Data Guard — the capability to open the standby for read-only access — is a separately purchased option requiring its own processor licences on the standby.

A common and costly mistake is for organisations to assume that Data Guard standbys are included in the primary licence. They are not. The Data Guard software is free; the hardware environment running it is not.

Multi-Site DR and Geographic Standby Configurations

Organisations with multiple data centres often implement geographic standby configurations — for example, a primary in London and a passive standby in Frankfurt. Each site's Oracle environment must be independently licensed. The fact that the Frankfurt standby is rarely or never the active database does not reduce the licence obligation: if it is running and applying logs, it must be fully licensed.

For multi-site configurations where Oracle Real Application Clusters (RAC) is used across sites, the licensing complexity increases further. RAC requires all nodes in the cluster to be licensed, and RAC One Node — a more limited version — has its own configuration rules. Organisations that implement stretched clusters or multi-site RAC as a DR strategy often discover that their licence obligations are significantly larger than anticipated.

Oracle's Approach to DR Audits

Oracle's LMS (Licence Management Services) collection scripts are designed to discover all environments where Oracle software is running — including standby databases. During an audit, LMS scripts run against all database servers and report the Oracle processes running on each host. A warm standby running continuously in managed recovery mode will show active Oracle processes and will be included in the processor count.

A common audit scenario: an organisation believes its Data Guard warm standby is exempt because it "isn't really being used." Oracle's LMS scripts show continuous Oracle processes running on the standby host. The audit team counts the standby host's processors and raises a compliance claim for unlicensed processors equal to the full standby environment. The initial claim often runs to seven figures for large enterprise databases.

For Active Data Guard, the exposure is compounded. If a team has been offloading read-only queries to a standby that is not licensed for Active Data Guard, Oracle's auditors calculate the ADG option cost on all standby processors for the licence term — potentially five or more years of back-support fees at 8% annual increases compounded over the period.

Practical Strategies for DR Licence Compliance

Managing Oracle DR licensing does not require abandoning your resiliency architecture — it requires understanding what you have and making informed decisions about how to structure it. The following strategies represent the most effective approaches our advisors have seen across hundreds of Oracle engagements.

• Conduct a DR environment inventory before your next Oracle support renewal. Map every server running Oracle software in a standby capacity, identify whether it is cold, warm, or active, and compare against your current licence position.
• Consider cold standby where RTO allows. If your business can tolerate a longer recovery time in exchange for a lower licence cost, a true cold standby eliminates the continuous-running obligation. The trade-off is a longer failover window — but for non-critical systems, this may be acceptable.
• Negotiate DR licence discounts at renewal. Oracle does offer negotiated discounts for passive DR environments — typically in the range of 50-75% off list price for a designated, passive-only DR database. These discounts are not offered proactively; they require negotiation with contractual protections around the passive-only use obligation.
• Evaluate Oracle Cloud for DR workloads. OCI's Universal Credits model can reduce the cost of running Oracle Database in DR configurations by using BYOL (Bring Your Own Licence) and paying only for compute consumed during actual DR testing and failover events, rather than for continuously running standby processors.
• Review Oracle CSI (Customer Support Identifier) records. Ensure your CSI accurately reflects all environments including DR. Discrepancies between your CSI and your actual deployment create audit exposure and complicate support claims.

The 10-Day Rule: What It Does Not Cover

To summarise the boundaries of the 10-day exemption clearly: it does not apply to warm standbys (continuously running in log-apply mode), active standbys (opened for read-only access), multi-node standby clusters, any standby outside a clustered configuration with shared storage, or any failover that exceeds 10 cumulative calendar days per year. For most enterprise Oracle DR architectures, the 10-day rule is simply not applicable — the organisation's DR environment requires full processor licensing.

Frequently Asked Questions

Does Oracle Data Guard require a separate licence?

Oracle Data Guard software itself is included with Oracle Database Enterprise Edition. However, the standby database running under Data Guard must be separately licensed if it is continuously running — the software is free, but the processor infrastructure is not.

Can I use the 10-day rule for planned DR tests?

Yes, but the days consumed during planned testing count towards the annual 10-day allowance. If you test quarterly with each test lasting 3 days, you exhaust your annual allowance after the first test. Subsequent activations require a fully licensed standby.

Does Oracle's 8% annual support increase apply to DR licences?

Yes. Annual support fees (Software Update Licence and Support) increase at 8% per year. This applies to primary and standby environment licences alike, making multi-year DR licensing costs significantly higher than the first-year support figure suggests.

Is Active Data Guard worth the cost?

Active Data Guard at $11,500 per processor is expensive. For organisations that actively use the standby for reporting, analytics, or read-only workloads, the cost may be justified. For organisations that have inadvertently enabled read-only access without licensing, negotiated remediation at less than full list price is often achievable with skilled advisory support.