Oracle gives one narrow break for disaster recovery: a clustered failover node may run unlicensed for up to ten days a year. Almost everything else needs a full license. Read the boundary before you build the runbook.
Oracle disaster recovery licensing rests on one narrow allowance. A clustered failover node may run unlicensed for up to ten days a year. Standby copies, remote mirrors, and opened backups all need full licenses.
The rule is a single, narrow allowance for unplanned failover inside a cluster.
When production fails, Oracle permits one otherwise unlicensed node in the same cluster to run the database for up to a total of ten separate days in a calendar year. Oracle sets this out in the Oracle Software Investment Guide.
Past ten days, the failover node needs a full license. The rule never covers planned testing, reporting, or load balancing.
Yes. A standby is a separate copy of the database, so it carries its own full license.
A Data Guard standby applies redo on separate storage. It is a deployment in its own right and needs the same Enterprise Edition license and options as production. See our Active Data Guard licensing guide.
Array based replication that copies the database to a remote site also needs a full license at the target, because Oracle software is installed and can run there. Oracle outlines the supported designs on its high availability page.
Oracle disaster recovery scenarios and the license they need
| DR scenario | License needed | Relief available | Note |
|---|---|---|---|
| Clustered failover, shared storage | One spare node free | Ten day rule | Counts whole days |
| Data Guard standby | Full license | None | Separate copy |
| Remote storage mirror | Full license | None | Software can run at target |
| Cold backup, never opened | No license | Backup exemption | Until you recover it |
| Failover test or DR drill | Full license | None | Not covered by ten day rule |
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Backups are fine until you use them. Testing is where teams trip.
A backup that is never mounted or opened does not need a license. The moment you recover and open it for use, it does. Oracle confirms the boundary in the Oracle Database Licensing Information manual.
A planned disaster recovery drill is not a failover event. It runs Oracle software for testing, so it needs a license on the node you test against.
The common advice is that the ten day rule makes most disaster recovery effectively free, so teams build a recovery site and assume no license cost. We disagree. In roughly 6 out of 10 estates we reviewed, the rule did not even apply, because the design used a separate standby copy or failed the shared storage condition, so the site was unlicensed and exposed. The buyer side move is to classify every recovery component against the actual rule before you call any of it free. A standby is licensable. A mirror is licensable. Only a true clustered failover on shared storage gets the ten days, and even then a DR drill burns no part of that allowance because it is not a failover.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Disaster recovery is the area buyers most often assume is free. The ten day rule is real, but it is narrow, and almost nothing about a standby qualifies for it.
Three moves remove most of the risk.
Label each node as clustered failover, standby, mirror, or backup. The label sets the license rule.
Confirm the failover node truly shares storage with production. If it does not, the ten day rule does not apply.
Log every failover event and the days used, so you can prove you stayed inside the ten day limit.
The ten day rule lets one otherwise unlicensed node in a cluster run Oracle during failover for up to ten separate days per calendar year. The failover node must share storage with production, and any part of a day counts as a full day.
No. A Data Guard standby is a separate copy of the database on its own storage. It is a deployment in its own right and must be fully licensed for Enterprise Edition and matching options, with no ten day relief.
Yes. Array based replication that copies the database to a remote site needs a full license at the target, because Oracle software is installed and can run there. The replication method does not change the licensing position.
A backup that is never mounted or opened does not need a license. The moment you recover and open it for use, it becomes a running deployment and needs a full license like any other.
A drill needs its own license but does not consume the ten day failover allowance, because a planned test is not an unplanned failover event. Treat drills and real failovers as different cases in the runbook.
The failover node and production must share the same storage, only one spare node qualifies, and the relief covers a maximum of ten separate days a year. If any condition fails, the node needs a full license.
No. Only a true clustered failover on shared storage gets the narrow ten day allowance. Standby copies, mirrors, and opened backups all need full licenses, which is why many recovery sites are found underlicensed.
Log every failover event with dates and the node used. A documented failover record is the evidence that supports the ten day claim if Oracle questions it during an audit.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
