Oracle disaster recovery licensing the ten day rule.

Oracle disaster recovery licensing turns on one question: is the standby server doing any work, or is it truly cold? The answer decides whether you pay nothing or pay full price.

This guide is for infrastructure and license teams designing Oracle high availability. Read it with the Oracle disaster recovery cloud licensing page and the Oracle Database licensing guide.

Oracle DR licensing is one of the few areas where a design choice removes cost entirely. The rules are narrow, so the design has to match them exactly or the exemption evaporates.

What is the Oracle ten day failover rule?

Oracle allows a license to follow a workload to a failover node for up to ten separate days in a calendar year, provided the failover node is in the same cluster and is otherwise unlicensed.

What counts as a failover day?

Any part of a day the node runs the workload counts as one full day. Ten such days exhaust the allowance. The eleventh day means the standby node needs its own full licenses.

• Same cluster: the rule only applies inside one failover cluster.
• Ten days: separate days, not hours, across the calendar year.
• Unlicensed node: the failover node holds no Oracle licenses of its own.

What does the ten day rule not cover?

The Oracle data recovery licensing policy excludes testing, reporting, and backups taken on the standby. Only genuine failover counts toward the allowance.

How does each standby configuration change licensing?

Not all standby is equal. A cold archive that never opens behaves very differently from an Active Data Guard replica serving read queries. The license cost tracks the activity.

When is a standby truly cold?

A cold standby holds disks that are not mounted and a database that is not open. Nothing runs until a failover. This is the configuration the ten day rule was written for.

Why does Active Data Guard cost more?

Active Data Guard opens the standby for read only queries and adds an option fee on top of the base license. Both primary and standby need full Database licenses plus the Active Data Guard option.

• Basic Data Guard: included with Enterprise Edition, standby stays mounted.
• Active Data Guard: separately licensed option, standby open for reads.
• Snapshot standby: opens for testing and ends the cold exemption.

A cold standby with disciplined failover can cost nothing. An always open replica doubles your license count.

How does disaster recovery licensing work in the cloud?

Moving DR to AWS, Azure, or OCI does not remove the usage test. It changes how you count cores and which policy document applies.

How are cores counted for cloud DR?

On authorized clouds you count vCPUs, two to a license with hyperthreading on. A cold cloud standby that never opens can still use the failover allowance, but an open replica needs full licenses.

What is the common cloud DR trap?

Teams leave a cloud standby open for monitoring or reporting. That single choice converts a free cold standby into a fully licensed second environment. Keep it closed unless you accept the cost.

What buyer side moves protect a DR design?

DR licensing rewards discipline. Document the design, prove the failover days, and keep the standby genuinely idle when it is meant to be cold.

Why does evidence matter so much?

In an audit the customer must prove the standby was cold and that failover stayed inside ten days. Failover logs, mount records, and change tickets are the evidence Oracle accepts.

Which design choice saves the most?

Keeping DR cold rather than active. A cold standby with disciplined failover can cost nothing. An always open replica doubles the license count for the comfort of instant reads.

Suggested reading

• Oracle DR cloud licensing. Cross vendor reading from the wider library.
• Oracle Database licensing guide. Cross vendor reading from the wider library.
• Oracle Database licensing on AWS. Cross vendor reading from the wider library.

What to do next

1. Inventory every standby and classify it as cold, mounted, or open.
2. Confirm which standby nodes sit in the same cluster as their primary.
3. Count failover days per node for the current calendar year.
4. Identify any Active Data Guard use that needs the separate option license.
5. Close cloud standbys used only for monitoring or reporting.
6. Build a failover evidence pack with logs, mount records, and tickets.
7. Review the DR design against the policy before the next audit cycle.

Frequently asked questions

Does a cold Oracle standby need a license?

Not always. A truly cold standby in the same cluster can use the ten day failover rule and need no license, provided failover stays inside ten separate days a year and the node is otherwise unlicensed.

How many failover days does Oracle allow for free?

Up to ten separate days in a calendar year. Any part of a day counts as a full day, and the eleventh day means the failover node must carry its own full Database licenses.

Does Active Data Guard require extra licensing?

Yes, Active Data Guard is a separately licensed option on top of the full Database license, and both the primary and the open standby need to be fully licensed for the base database and the option.

Does the ten day rule cover testing on the standby?

No, the rule covers genuine failover only. Testing, reporting, and opening the standby as a snapshot all fall outside the allowance and require the standby to be fully licensed.

How is cloud DR licensing different?

The usage test is the same, but you count vCPUs instead of cores. A cold cloud standby can still use the failover allowance, while an open cloud replica needs full licenses just like on premise.

Who proves the standby was cold in an audit?

The customer carries the burden of proof. Failover logs, disk mount records, and change tickets are the evidence Oracle accepts, so capture them continuously rather than reconstructing after a request.