Independent advisory guide covering Data Guard vs Active Data Guard, licensing both primary and standby environments, Processor vs Named User Plus calculations, the 10-day failover rule, virtualization pitfalls, cloud BYOL, and cost optimisation strategies. The line between free Data Guard and paid Active Data Guard is a single database open mode. This guide shows you exactly where that line is.
This guide is part of our Oracle Database licensing coverage. See also: Oracle Database Licensing Guide | Failover & DR Licensing | NUP vs Processor | Core Factor Table
Oracle Active Data Guard (ADG) is a separately licensed Enterprise Edition option that transforms a passive disaster recovery standby database into an active, productive asset. While standard Data Guard, included free with Oracle Database Enterprise Edition, maintains a synchronised standby for failover, ADG goes further by allowing that standby to serve read-only queries, run backups, and provide real-time reporting while continuously applying redo from the primary database.
For licensing professionals, the distinction matters enormously. Data Guard itself costs nothing beyond your Enterprise Edition licence. The moment you open that standby for read-only queries, or enable any ADG feature such as real-time query, automatic block repair, Far Sync, or DML redirection, you enter Active Data Guard territory. Oracle requires a separate, paid option licence on every environment involved. For a comprehensive overview of all Oracle Database editions and options, see our Oracle Database Licensing Guide.
Real-Time Query allows read-only workloads (reports, ad-hoc selects, analytics) to run on a synchronised standby database. This offloads the primary, provides read scalability, and continuously validates failover readiness.
Automatic Block Repair transparently fixes physical data block corruption on either the primary or standby by fetching the correct block from the other database.
Far Sync enables zero-data-loss protection over long distances by shipping redo to a lightweight Far Sync instance, which then forwards it to the actual standby.
Fast Incremental Backup offloads RMAN backups to the standby using Block Change Tracking, improving backup performance by up to 20x without impacting the primary.
DML Redirection (Oracle 19c+) allows certain write operations on the read-only standby by transparently forwarding them to the primary, enabling application flexibility while maintaining data consistency.
Rolling Upgrades allow the standby to apply patches and database upgrades, then switch roles with the primary, minimising downtime during maintenance windows.
Active Data Guard is one of the most commonly mis-licensed Oracle options we encounter. Organisations deploy Data Guard (which is free), then enable read-only access on the standby without realising they have crossed into ADG territory. By the time Oracle's audit team arrives, the exposure can be hundreds of thousands of dollars. The licensing line between "free" and "paid" is a single database open mode. Oracle knows exactly how to find it.
The boundary between free Data Guard and paid Active Data Guard is the single most important licensing distinction for disaster recovery environments. Getting it wrong in either direction costs real money.
| Aspect | Oracle Data Guard (Free) | Active Data Guard (Paid) |
|---|---|---|
| Licence required? | No. Included with Enterprise Edition. | Yes. Separate EE option: $11,500/processor or $230/NUP. |
| Primary use | Maintain standby for failover/DR. Standby not open during normal operations. | Offload read workloads, reporting, backups to synchronised standby. |
| Standby open read-only? | Not while applying redo. Opening breaks recovery continuity. | Yes. Open read-only and applying redo simultaneously. |
| Real-Time Query | No | Yes. Up-to-date query results from standby. |
| Automatic Block Repair | No | Yes. Corrupt blocks repaired automatically. |
| Far Sync / DML Redirection | No | Yes. Zero-data-loss over distance; write forwarding. |
| Licensing scope | Covered by DB EE licence. No extra cost. | Must licence both primary and standby environments. |
Critical distinction. The standby database in a standard Data Guard configuration must remain in mount state (not open for read). If you open it for read-only access while redo is being applied, you are using Active Data Guard, regardless of whether you intended to. Oracle's LMS audit scripts detect the database open mode and will flag this as unlicensed ADG usage.
For detailed guidance on how Oracle handles standby and failover environments, see our Oracle Failover Licensing and Disaster Recovery Guide.
Oracle Active Data Guard is priced as a standard Enterprise Edition option. The list prices, taken from the Oracle Technology Price List, are as follows.
| Licence Metric | List Price | Annual Support (22%) | Total Year 1 Cost |
|---|---|---|---|
| Processor | $11,500 per processor | $2,530 per processor | $14,030 per processor |
| Named User Plus | $230 per NUP | $50.60 per NUP | $280.60 per NUP |
These prices apply per environment. Since Oracle requires ADG to be licensed on both the primary and each standby server, the effective cost doubles for a typical single-primary, single-standby configuration.
Real-world cost example. Consider an organisation running Oracle Database EE on a 2-socket Intel server with 16 cores per socket (32 total cores). Using Oracle's 0.5 core factor for Intel x86 processors, this translates to 16 processor licences. For a detailed walkthrough, see our Oracle Core Factor Table guide.
| Component | Primary Server | Standby Server | Total |
|---|---|---|---|
| Cores | 32 (Intel) | 32 (Intel) | 64 |
| Core Factor (0.5) | 16 processors | 16 processors | 32 processors |
| ADG licence cost | $184,000 | $184,000 | $368,000 |
| Annual support | $40,480 | $40,480 | $80,960 |
| Year 1 total | $224,480 | $224,480 | $448,960 |
This is in addition to the Oracle Database EE licence cost ($47,500 per processor list price). The combined DB EE + ADG cost for this configuration would exceed $2M at list price, before any negotiation.
Enterprise customers rarely pay list price for Active Data Guard. In large Oracle deals, ADG is often bundled into a ULA or negotiated as part of a broader database contract. Discounts of 50 to 70% off list are achievable when ADG is part of a multi-million-dollar Oracle commitment. The key is to negotiate ADG alongside the database licence, not as an afterthought add-on where Oracle has maximum pricing leverage.
Oracle offers two licensing models for ADG: Named User Plus (NUP) and Processor. The choice must match how your Oracle Database Enterprise Edition is licensed. You cannot mix metrics. For a comprehensive comparison, see our guide on Named User Plus vs Processor licensing.
| Factor | Named User Plus | Processor |
|---|---|---|
| Pricing | $230 per named user | $11,500 per processor (after core factor) |
| Best for | Small, known user populations (10 to 50 DBAs/analysts) | Large or unknown user counts; public-facing systems |
| Minimum requirement | 25 NUP per processor (EE minimum) | Must cover all cores on each server (with core factor) |
| User tracking | Must count all individuals/devices accessing the DB | Unlimited users. No counting required. |
| Cost breakeven | Cheaper when users < ~50 per processor | Cheaper when users > ~50 per processor |
The minimum NUP trap. Oracle requires a minimum of 25 Named User Plus licences per processor for Enterprise Edition and all its options, including ADG. Even if only 5 DBAs access the standby for reporting, if the standby server has 4 processors (after core factor), you need at least 100 NUP licences (4 x 25). At $230 each, that is $23,000, compared to $46,000 for 4 processor licences at list. NUP appears cheaper, but the minimum requirement narrows the gap significantly. See our detailed analysis of Oracle NUP minimum requirements.
Matching the primary database metric. The ADG licence metric and quantity must match or exceed the primary database licence. If your primary DB is licensed for 100 NUP, ADG needs at least 100 NUP. If the primary has 8 processor licences, ADG needs at least 8 per environment. This matching principle prevents organisations from gaming the metric by choosing a cheaper model for the option than for the base product.
Oracle's ADG licensing rules are specific and strictly enforced during audits. Misinterpreting any of them can create significant compliance exposure.
Rule 1: Enterprise Edition only. Active Data Guard is exclusively an Enterprise Edition option. It cannot be used with Standard Edition 2 databases (which lack Data Guard entirely). For a comparison of editions, see our Oracle Database Licensing Guide.
Rule 2: Licence both primary and standby. This is the rule that catches most organisations off-guard. Oracle requires the ADG option to be licensed on both the primary database server and every standby server in the Data Guard configuration. The rationale is that the primary actively participates in ADG features (sending redo, supporting block repair, handling DML redirection). If you have one primary and two active standbys, you need ADG licences on all three environments.
Rule 3: Matching metric and quantity. The licensing metric (NUP or Processor) must be identical to the primary database metric. The quantity must be at least equal. You cannot licence ADG for fewer users or processors than the database itself.
Rule 4: Per-server core calculations. When licensing by Processor, calculate the requirement for each server independently based on its own hardware. If the primary runs on a 32-core server (16 processors after core factor) and the standby on a 16-core server (8 processors), licence 16 ADG processors for the primary and 8 for the standby.
Rule 5: No partial licensing. You cannot license ADG on just the standby or just the primary. If ADG features are active anywhere in the Data Guard configuration, every participating database needs the option licence. Similarly, you cannot license ADG for only some standbys in a multi-standby configuration.
Rule 6: All environments include non-production. If you enable ADG features in development, test, or QA environments, those environments also need ADG licences. Oracle provides no free-use exception for ADG in non-production settings (unless covered under specific contract terms like a ULA).
Oracle's LMS audit scripts check the DBA_FEATURE_USAGE_STATISTICS view, which records whether Active Data Guard features have been used, including specific timestamps. Even if you disabled ADG features before the audit, the historical usage data remains visible. Oracle will use this evidence to demand licences for the entire period of usage.
Oracle provides a limited licensing exemption for purely passive disaster recovery standby databases. This is often called the "10-day rule" and it applies to the base database licence. Critically, it does not apply when Active Data Guard is in use.
How the 10-day rule works. Oracle permits a single failover standby database to operate without a separate database licence for up to 10 separate days (24-hour periods) per year. This covers genuine disaster recovery activations and brief failover tests. Any usage beyond 10 days requires the standby to be fully licensed. Only one failover node qualifies, and any activation, including maintenance, patching, or testing, counts against the limit.
Why the 10-day rule does not apply to ADG. The failover exemption is designed for passive standbys that remain in mount state during normal operations. When you use Active Data Guard, the standby is by definition active: open for read-only queries, running backups, applying redo in real-time. This continuous active usage means the standby must be fully licensed for both Oracle Database EE and the ADG option from day one, regardless of the 10-day rule.
If you deploy a genuinely passive standby (no ADG features, database in mount state, activated only during emergencies), the 10-day rule can save you the cost of a full DB EE licence on that standby. The moment you add ADG capabilities, that savings disappears. For complete failover and DR licensing details, see our Oracle Disaster Recovery Licensing Guide.
We see organisations try to claim the 10-day failover exemption while simultaneously running Active Data Guard on the standby. This is contradictory. You cannot be "passive for failover purposes" and "active for real-time query" at the same time. Oracle's audit team will identify this immediately and demand full licensing for both the database and the ADG option, often with back-dated support charges. If you want the DR cost savings, keep the standby truly passive.
Virtualization is where Active Data Guard licensing becomes genuinely dangerous, and where the largest compliance gaps typically appear. Oracle's virtualization rules apply to ADG exactly as they do to the base database licence.
Soft partitioning: the full-cluster liability. Oracle classifies VMware vSphere, Microsoft Hyper-V, Docker containers, and most common hypervisors as soft partitioning. Under Oracle's policy, soft partitioning cannot be used to limit licensing scope. If your Oracle database runs on a VM with 4 vCPUs within a VMware cluster of 5 hosts (each with 16 cores), Oracle's position is that you must license all 80 cores across the entire cluster.
For Active Data Guard, this liability applies to both the primary and standby environments. If both run on VMware clusters, you could face ADG licensing requirements across two full clusters, potentially hundreds of cores. For a comprehensive treatment, see our Oracle Partitioning Policy guide and our Oracle Licensing in Virtualised Environments article.
Hard partitioning: the safe path. Oracle recognises a limited set of technologies as hard partitioning: Oracle VM (with CPU pinning), Oracle Linux KVM (with hard partitioning), IBM LPAR, and Solaris Zones. When properly configured, hard partitioning allows you to license only the cores allocated to Oracle, dramatically reducing the ADG licence requirement.
Dedicated Oracle clusters. If you must run on VMware, create isolated VMware clusters exclusively for Oracle workloads. Pin Oracle VMs to these clusters with strict affinity rules and document that Oracle VMs cannot migrate to other clusters. While not a bulletproof defence against Oracle's full-cluster policy, it significantly reduces the scope of any licensing claim.
Physical servers for standby. In some cases, running the standby database on a dedicated physical server (rather than a shared VM cluster) is cheaper once you factor in ADG licensing costs across a virtual environment. The hardware cost may be lower than the licensing premium.
Oracle VM or KVM. Migrating ADG workloads to an Oracle-approved hypervisor can cut licensing costs by 70 to 90% compared to licensing an entire VMware cluster.
Oracle's ADG licensing rules apply equally in cloud environments. Whether you deploy on Oracle Cloud Infrastructure (OCI), AWS, or Azure under a Bring Your Own License (BYOL) model, Active Data Guard must be properly licensed.
Oracle Cloud Infrastructure (OCI). OCI offers the most favourable licensing terms. Under BYOL, 1 OCPU = 1 Oracle processor licence. If you activate 8 OCPUs for a database, you need 8 ADG processor licences per environment. Alternatively, OCI offers a license-included subscription where ADG can be enabled as a cloud service add-on for an additional hourly charge.
AWS and Azure (Authorised Cloud Environments). On AWS and Azure, Oracle's Authorised Cloud Environment policy applies. The standard conversion is 2 vCPUs = 1 processor licence (assuming hyper-threading is enabled). For ADG BYOL on a 16-vCPU EC2 instance, you need 8 processor licences for the database and 8 additional ADG processor licences per environment. The Oracle Core Factor Table does not apply in cloud environments; the simplified vCPU conversion rule applies instead.
Cloud DR architecture implications. Many organisations use cross-region Data Guard replication in the cloud for disaster recovery. If the DR region's standby uses ADG features (even just read-only reporting), it must be fully licensed. Cloud deployment is not a licensing loophole. Oracle's BYOL compliance checks will verify that you have sufficient ADG licences to cover all cloud instances where ADG is active.
These are the mistakes we encounter most frequently in ADG licensing engagements. Each one can result in six- or seven-figure compliance exposure.
1. Assuming Data Guard = Active Data Guard. Opening a standby database for read-only reporting requires the ADG option licence. Data Guard is free; the "Active" capability is not. This is the single most common ADG compliance violation, and Oracle's audit scripts specifically detect standby database open modes.
2. Not licensing the standby environment. Oracle requires ADG licences on both the primary and the standby. Licensing only the primary (or undercounting the standby's cores) leaves a compliance gap. Calculate licence requirements for each server independently.
3. Mixing licence metrics. Using NUP for the primary database and Processor for ADG (or vice versa) violates Oracle's matching requirement. All database options must follow the same metric as the base product. This creates a messy compliance situation that is expensive to unwind.
4. Ignoring NUP minimums. Even if only 8 DBAs access the standby, the 25-NUP-per-processor minimum applies. On a 4-processor server, you need at least 100 NUP licences regardless of actual user count. Failing to meet minimums is a compliance violation.
5. VMware full-cluster licensing failures. Running ADG on a VM in a shared VMware cluster without understanding Oracle's soft partitioning policy can result in licensing demands for every core in the cluster. This single mistake regularly generates $1M+ audit findings.
6. Overlooking implicit ADG feature usage. Enabling Automatic Block Repair, DML Redirection, or Fast Incremental Backup on a standby may not be as obvious as opening the database read-only. But these are all ADG features that require licensing. Always cross-check which features are active on your standbys.
7. Claiming the 10-day rule while using ADG. The passive failover exemption does not apply when Active Data Guard is in use. If the standby is continuously synchronised and open for queries, it must be fully licensed from day one. There is no 10-day grace period for active standbys. See our Oracle Audit Strategic Guide for more on audit defence.
1. Assess before you enable. Before activating any ADG feature, perform a thorough licensing assessment. Calculate the total cost across all environments: primary, standby, and any non-production systems. Compare this against the business value of having an active standby. In some cases, a simple Data Guard configuration with a separate reporting database refreshed periodically is more cost-effective.
2. Right-size your hardware. Since ADG is licensed per processor, the standby server's core count directly drives cost. If the standby only serves read-only reporting, it may not need the same hardware specification as the primary. A smaller standby server (fewer cores) means fewer ADG processor licences.
3. Consolidate standby workloads. If you have multiple primary databases, you might not need ADG on every standby. Identify which databases genuinely benefit from active standby capabilities and which can use standard Data Guard. Licensing ADG on one strategic standby rather than five can save hundreds of thousands of dollars. For contract negotiation strategies, see our guide on managing Oracle contracts.
4. Use hard partitioning where possible. In virtualised environments, migrating ADG workloads to Oracle-approved hard partitioning technologies (Oracle VM, Oracle Linux KVM) can reduce licensing scope from full cluster to pinned cores. Often a 60 to 80% cost reduction. The migration cost is almost always less than the licensing savings.
5. Document everything. Maintain clear records of every environment where ADG is (and is not) deployed. Document hardware specifications, core counts, core factors, standby database open modes, and the business purpose of each standby. Distinguish clearly between passive Data Guard standbys and active ADG standbys. This documentation is your primary defence in an audit.
6. Run internal audits regularly. Oracle's LMS scripts detect ADG feature usage via DBA_FEATURE_USAGE_STATISTICS. Run these scripts internally, quarterly at minimum, to catch accidental ADG usage (e.g., a DBA opening a standby for read-only access without realising the licensing implications). Proactive identification allows you to remediate before Oracle's audit team finds it.
7. Negotiate ADG into broader deals. Never purchase ADG as a standalone add-on after the initial database purchase. The best discounts come when ADG is included in the original database contract, a ULA, or a broader Oracle negotiation. Leverage competitive pressure (third-party replication tools, cloud-native DR) to drive down ADG pricing.
A large insurer was licensing Active Data Guard across six database environments: four production and two development. Our review found that three of the production standbys were only used for failover (not active reporting) and both development environments had ADG enabled accidentally by DBAs. We deactivated ADG on five environments, properly documented the Data Guard configurations, and negotiated the single remaining ADG deployment at a 55% discount. Annual savings: $890K in licence and support costs eliminated.
Oracle Active Data Guard is a separately licensed add-on to Oracle Database Enterprise Edition that enhances standard Data Guard by allowing a physical standby database to be open for read-only queries and backups while continuously applying redo from the primary. Key features include real-time query, automatic block repair, Far Sync, fast incremental backup offload, DML redirection, and rolling upgrades.
The list price is $11,500 per processor or $230 per Named User Plus, plus 22% annual support ($2,530/processor or $50.60/NUP). Both the primary and standby environments must be licensed, effectively doubling the cost. Enterprise customers typically negotiate 50 to 70% discounts when ADG is part of a larger Oracle deal. For pricing details, see the Oracle Technology Price List guide.
Yes. Oracle requires Active Data Guard to be licensed on every environment in the Data Guard configuration: both the primary and all standbys that use ADG features. The primary participates in ADG through redo transport, block repair, and DML redirection, so Oracle considers it part of the ADG deployment.
Yes. Standard Data Guard, which provides redo transport, managed failover, and standby maintenance, is included with Enterprise Edition at no extra cost. The standby must remain in mount state (not open for read-only). The moment you enable Active Data Guard features (open read-only while applying redo, block repair, Far Sync, etc.), you need a separate ADG licence.
Yes. If the standby database is open for read-only access while simultaneously applying redo logs from the primary, that is an Active Data Guard feature (real-time query) and requires the ADG option licence on both environments. If you open the standby read-only without applying redo, you are technically using standard Data Guard, but you lose real-time data currency.
Yes, provided the primary database is also licensed by NUP. However, Oracle's minimum of 25 NUP per processor still applies. Even with a handful of users, the minimum can push the required licence count well above your actual user population. Always model both NUP and Processor costs before choosing. See our NUP minimum requirements guide.
No. The 10-day rule is designed for purely passive standby databases that are normally idle and only activated during genuine failover events. If Active Data Guard is in use (standby open for queries, backups running on standby, etc.), the standby is actively contributing and must be fully licensed from day one. For detailed DR rules, see our Failover Licensing Guide.
Oracle classifies VMware as soft partitioning, meaning all physical cores in a VMware cluster (or all hosts where Oracle VMs could run) may need to be licensed. This applies to ADG on both primary and standby environments. Isolating Oracle VMs on dedicated hosts or clusters, and using Oracle-approved hard partitioning where possible, can significantly reduce exposure. See our Oracle Partitioning Policy guide.
Under BYOL, ADG licences must cover all cloud instances where ADG is active. On OCI, 1 OCPU = 1 processor licence. On AWS/Azure, 2 vCPUs = 1 processor licence (with hyper-threading). The Core Factor Table does not apply in authorised cloud environments. ADG must be licensed on both the primary and standby cloud instances.
Oracle will demand back-dated licence fees plus support (at list price, typically without discount) for the entire period of unlicensed usage. This can include years of back-support at 22% annually. The audit findings can be substantial. We have seen six- and seven-figure ADG compliance claims. Proactive internal auditing and proper documentation are the best protection. See our Oracle Audit Strategic Guide.
Yes. If your primary need is read offload or reporting, there are alternatives to ADG, including third-party replication tools (Oracle GoldenGate, Dbvisit Standby, Quest SharePlex) or periodically refreshed reporting databases. These may have their own licensing implications, but they can be significantly cheaper than ADG for the same functionality. We recommend modelling the total cost of ownership for each approach.
Query the DBA_FEATURE_USAGE_STATISTICS view in your Oracle Database. Look for entries related to "Active Data Guard" features. Also check whether any standby databases are open in READ ONLY WITH APPLY mode (which indicates ADG usage). Oracle's own LMS collection scripts gather this same data during audits. Running these checks internally first ensures you can remediate before Oracle identifies any gaps.
Our Oracle advisory team has helped hundreds of enterprises right-size ADG deployments, defend against audits, and negotiate favourable terms. Typical savings: 40 to 70% versus Oracle's initial demands. Independent. Fixed-fee. No Oracle bias.
Oracle Advisory ServicesIndependent Oracle licensing advisory. ADG compliance assessment, audit defence, cost optimisation. Fixed-fee. Vendor-independent.