Active Data Guard licensing, the standby rule and the line
Active Data Guard is a paid option on Enterprise Edition, and the standby it protects must carry the same licenses as production, option for option. Most of the money is decided by two things: whether the standby is licensed at all, and the exact moment a mounted standby becomes an active one, a line one V$DATABASE value marks precisely.
Prepared by Redress Compliance · August 6, 2026 · Oracle advisory. Based on 30 to 40 database estates reviewed 2024 to 2026.
Executive summary
The option is the small number. Active Data Guard lists at $11,500 per processor plus 22 percent support; the bigger number is usually the second Enterprise Edition license the standby itself requires, $47,500 per processor, matched to production. Basic Data Guard ships included with EE, and the whole licensing question is which side of one line your standby operates on.
The line is read only with apply. The option is triggered when the standby is open for reading while redo apply is running, the state V$DATABASE reports as read only with apply. Opening a physical standby read only with basic Data Guard is allowed, provided redo apply is stopped first, which means periodic reporting can live inside the free rule, and continuous real time query cannot.
Option symmetry multiplies the standby. The standby applying redo needs the options production runs: Partitioning, the Diagnostics Pack, and the rest, which is where four figure options become six figure ones. And if the standby sits on a shared virtualization cluster at the DR site, Oracle's partitioning position can make the standby count more processors than production, the DR estate inheriting the cluster's core count.
The findings run both directions. Across our reviews, the most common single finding was a standby open for reading with no option on the contract, and in about 6 of 10 estates the disaster recovery standby was not correctly licensed at all, in one direction or the other: active use on basic entitlements, or full stacks purchased for mounted standbys the free rules already covered.
The line, what is free and what is not
| The capability | Basic Data Guard, included | Active Data Guard, $11,500 |
|---|---|---|
| Redo apply to a physical standby | Included | Included |
| Switchover and failover | Included | Included |
| Snapshot standby, mounted standby backups | Included | Included |
| Standby open read only, apply stopped | Included: the periodic reporting rule | Included |
| Standby open read only while apply runs | Not included: the line itself | The core entitlement: real time query |
| Automatic block repair, far sync, standby block change tracking | Not included | Included |
The standby rule, symmetry option for option
The standby server must carry the same licenses as production: the Enterprise Edition base at $47,500 per processor on its own hardware's count, and, by option symmetry, every option whose redo it applies, Partitioning, Advanced Compression, the packs, each at its own rate. The symmetry is what converts a modest DR decision into the estate's second largest line, and the DR licensing analysis works the failover windows and the ten day rule that bound the exceptions. The free structures, snapshot standbys, mounted backups, switchover, cost nothing precisely because they keep the standby closed.
The database options and packs analysis
The full option catalog with Active Data Guard in context: the trigger states, the symmetry rules, the free lanes, and the remediation paths that avoid list price findings.
Get the white paper →The DR cluster trap, when the standby outcounts production
The DR site's economics invite consolidation: standbys parked on a shared virtualization cluster, sized for the disaster that has not happened. Oracle's partitioning position then counts what the standby could run on, the cluster, not the pinned VM, and the standby's licensable count exceeds production's, the virtualization licensing arithmetic landing on the estate least prepared for it. The defenses are the standard ones, dedicated DR hosts or clusters with the paper trail, decided when the DR site is designed rather than when the audit prices it.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across ADG reviews, 2024 to 2026
Across roughly 30 to 40 Oracle Database estates Fredrik Filipsson reviewed between 2024 and 2026, the standby was the cost driver in most cases, not the option:
Active use on basic entitlements in one direction, full stacks bought for mounted standbys the free rules covered in the other.
A standby open for reading with apply running and no option on the contract, V$DATABASE holding the evidence.
The overspend direction deserves equal billing: estates that licensed full production stacks for standbys that only ever mounted, backed up, and waited, paying option symmetry for databases the free structures already covered. The quarterly check is one query per standby, the V$DATABASE open mode against the entitlement, the same script output discipline the whole option estate runs on, priced against the price list both directions.
Your first five moves
- Query V$DATABASE on every standby, quarterly: the open mode against the entitlement, because read only with apply is the finding and the evidence.
- Use the free lane deliberately: apply stopped, open read only for the reporting window, apply resumed, documented as the operating procedure.
- License the symmetry or break it: the standby carries production's options, so the options estate on production is the standby's bill too.
- Fix the DR cluster boundary at design time, dedicated hosts or affinity with the paper trail, before the standby outcounts production.
- Sweep the overspend direction too: mounted standbys carrying full stacks are refunds waiting for a renewal. The Oracle practice runs the standby estate with you, both directions.
Frequently asked questions
How is Oracle Active Data Guard licensed?
As a paid Enterprise Edition option at $11,500 per processor plus 22 percent support, on top of the standby's own EE license at $47,500 per processor, matched to production option for option. Basic Data Guard, redo apply, switchover, failover, and snapshot standbys, ships included with Enterprise Edition.
When does a standby need the Active Data Guard option?
When it is open for reading while redo apply is running, the state V$DATABASE reports as read only with apply. That single state is the line: real time query, automatic block repair, far sync, and standby block change tracking need the option, and everything that keeps the standby closed or pauses apply does not.
Can we run reports on a standby without Active Data Guard?
Yes, inside the free lane: stop redo apply, open the standby read only, run the reporting window, and resume apply. Periodic reporting lives legally inside basic Data Guard at no option cost; only reading while apply runs, continuous real time query, crosses into the paid option.
Does the standby need the same options as production?
Yes, option symmetry applies: a standby applying redo from a production database running Partitioning or the Diagnostics Pack needs those options too, at their own rates, which is how four figure option decisions become six figure standby bills. The symmetry is the reason the standby, not the option, drives most of the cost.
Why might a standby count more processors than production?
The DR cluster trap: a standby on a shared virtualization cluster at the DR site counts, under Oracle's partitioning position, every core it could run on, the cluster rather than the VM. Dedicated DR hosts or documented affinity, decided at design time, keep the standby's count at its own hardware.
What is the most common Active Data Guard audit finding?
A standby open for reading with apply running and no option on the contract, present as the leading single finding across our reviews, with 6 in 10 estates incorrectly licensed in one direction or the other. The quarterly V$DATABASE check against entitlements is the whole prevention, in both directions.
