Oracle DR Cloud Licensing. Standby, failover, BYOL.

Oracle disaster recovery licensing carries four distinct rules. The 10 day failover rule for cold standby. Active Data Guard for managed standby with read access. OCI Autonomous Database Standby for managed DR on OCI. And BYOL math for DR on AWS or Azure.

Each rule has its own contractual basis and its own audit pattern. The 10 day rule is the most common audit finding, because customers stretch the rule past its scope.

Read this alongside the Oracle knowledge hub, the Oracle services, the Oracle Database licensing guide, and the Vendor Shield subscription.

The 10 day failover rule, line by line

The 10 day failover rule is the central to Oracle DR licensing. The rule lives in the Oracle Software Investment Guide and is enforced through the OMA or OLSA.

The rule, in plain language

• One standby per primary. One designated standby host per licensed primary host.
• 10 separate days per year. The standby may run for up to 10 separate days in any 365 day period without a separate license.
• Failover only. The standby runs when the primary is unavailable. Active active is not in scope.
• Designated host. The standby is a single named host. Multiple standby hosts require multiple licenses.
• 4 test events. Up to 4 testing events per year, each up to 2 days, do not consume the 10 day allowance.

Common audit findings on the 10 day rule

• Standby running 30 plus days. Standby kept hot for performance reasons beyond the 10 day allowance. Audit position: full license required.
• Read access on standby. Standby accessed for read traffic without Active Data Guard. Audit position: ADG license required at full processor list.
• Multiple standby hosts. Two or more standby hosts per primary. Audit position: each standby beyond the first requires a full license.
• Active active. Both nodes serving traffic. The 10 day rule does not apply.

Active Data Guard scope

Active Data Guard is the Oracle option that allows read access to the standby database while it is in recovery mode. The option is licensed at full processor list, 11,500 USD per processor.

What Active Data Guard covers

• Read only access to standby. Applications can run SELECT queries against the standby.
• Real time apply. Standby applies redo as it arrives, not after the primary commits the log.
• Snapshot Standby. Convert the standby to read write mode for testing without consuming the 10 day allowance.
• Far Sync. Lightweight log shipping intermediary for low latency standbys.

What Active Data Guard does not cover

• The Database license itself. ADG is an option on top of the Database license. The standby must carry a full Database EE license too.
• The 10 day rule. ADG is for read access during normal operations, not for failover. The 10 day rule still applies to the standby Database license.
• Active active. ADG is a passive standby with read access, not an active active configuration. For active active, use RAC.

OCI standby options

Oracle Cloud Infrastructure (OCI) offers managed standby through Autonomous Database and Database Cloud Service. The licensing model on OCI differs from on premise.

Autonomous Database Standby

• Local Autonomous Data Guard. Included in the Autonomous Database OCPU price. One standby in another availability domain in the same region.
• Cross region. Cross region standby is a separate paid feature, billed at the standby OCPU rate.
• Read access. Read access on the local standby is included.

Database Cloud Service Standby

• BYOL DBCS. Customer brings on premise license. Standby in another availability domain requires a separate BYOL license unless the 10 day rule applies.
• License Included DBCS. Standby in another availability domain billed at the Oracle Cloud OCPU rate.
• Exadata Cloud Service. Standby Exadata in another region billed per OCPU on the standby Exadata.

BYOL to AWS and Azure for DR

The Oracle Cloud Authorized License document defines the BYOL conversion rates for AWS, Azure, and Google Cloud. These rates apply to both primary and standby workloads.

AWS and Azure BYOL conversion

Platform	Instance type	Conversion rate
AWS EC2	General purpose vCPU	2 vCPU equals 1 Oracle processor
AWS EC2	Bare metal (m5.metal, m6i.metal)	1 socket equals 1 Oracle processor with core factor
AWS RDS	RDS instance vCPU	2 vCPU equals 1 Oracle processor
Azure VM	General purpose vCPU	2 vCPU equals 1 Oracle processor
Azure VM	Constrained core (E2as_v5 with constrained core)	Constrained cores count, not full socket
OCI	OCPU (one OCPU equals two vCPU)	1 OCPU equals 1 Oracle processor

DR specific BYOL rules

• Standby on AWS or Azure. The standby instance must carry a BYOL license at the same processor conversion as the primary, unless the 10 day rule applies.
• 10 day rule applies. The 10 day failover rule applies in cloud the same way as on premise. The standby may run up to 10 separate days per year without a separate license.
• Active Data Guard on cloud standby. ADG requires a separate ADG license at the standby BYOL processor count.

Worked example: 8 processor primary, hybrid DR

A retail customer runs an 8 processor Oracle Database EE primary on premise (Intel Xeon, 16 cores at 0.5 factor). The DR strategy is a hot standby on premise plus a cold standby on AWS EC2 for regional disaster.

License position

Component	Quantity	License	Annual support
Primary, on premise	8 processor EE	378K USD (post discount)	83K USD
On premise hot standby	8 processor EE plus ADG	0 USD (10 day rule limit met) + 184K USD ADG	40K USD ADG
AWS cold standby	8 processor BYOL on 16 vCPU EC2 m5	0 USD (10 day rule)	0 USD
Total	--	562K USD	123K USD

Key DR licensing rules applied

• 10 day rule on hot standby. The hot standby host carries no additional Database license because it stays inside the 10 day rule. The standby database is mounted but not running production traffic.
• ADG license for read access. The hot standby serves read traffic. That requires a full ADG license on 8 processors.
• AWS cold standby. The cold standby on AWS EC2 m5 carries a BYOL license, but stays inside the 10 day rule. No new license required.

Seven Oracle DR procurement levers

The seven DR levers buyer side carries to the deal

1. 10 day rule discipline. Document every failover event, every test event, and every 10 day reset. Auditable trail is the buyer side defense.
2. ADG license scope. Buy ADG only where the standby serves read traffic. Most DR architectures do not need ADG.
3. Standby designation. One standby per primary. Multiple standby hosts trigger multiple licenses.
4. OCI standby architecture. OCI Autonomous Database includes local standby. Cross region adds cost. Architect to minimize cross region.
5. BYOL math. Map every cloud DR workload to the Authorized List conversion. AWS m5.metal at 1 to 1 socket equals the lowest cost cloud DR for high CPU workloads.
6. Test event tracking. 4 test events per year, 2 days each, do not consume the 10 day allowance. Document every test.
7. Renewal trade. Trade DR architecture against a license harmonization, with explicit standby and failover rights written into the renewal order.

What to do next

The seven step checklist takes an Oracle DR licensing position from current state to a controlled architecture.

1. Inventory the DR topology. Every primary, every standby, every test environment, every region.
2. Document failover events. Every failover, every test, every day count by primary.
3. Validate the 10 day rule. Confirm every standby stays inside the rule. Surface any standby running hot beyond 10 days.
4. Audit ADG scope. Confirm ADG license matches read access points.
5. Map cloud DR to BYOL conversion. AWS, Azure, GCP, OCI. Confirm processor math.
6. Build the effective license position across primary, standby, test, and cloud.
7. Open the negotiation. Write explicit DR rights into the renewal order. Standby, failover, test events, BYOL conversion.

Frequently asked questions

How Redress engages on Oracle disaster recovery licensing

Redress runs Oracle DR licensing advisory inside the Vendor Shield subscription, the Oracle services, the Software Spend Assessment, and the Renewal Program.

Read the related Oracle hub, the Oracle Database licensing guide, the Oracle in cloud licensing, the virtualization guide, the Oracle on AWS guide, the ULA negotiation guide, the audit services, the licensing consultants guide, the benchmarking page, the about us page, and the contact page.