Data Guard and Active Data Guard: What Is the Difference?
Oracle Data Guard is Oracle's primary technology for database high availability, data protection, and disaster recovery. It maintains a synchronised copy — a standby database — of a primary Oracle Database at a secondary location, using Oracle's redo log streaming to keep the standby current with all primary database changes.
The key distinction for licensing purposes is between two modes of standby database operation:
Standard Data Guard (Physical Standby, Mounted Mode): The standby database receives and applies redo from the primary but is in "mounted" state — it is not open for query or access by users. It is purely a recovery target. Historically, Oracle took a more lenient position on licensing for purely passive standbys, but this position has been progressively hardened in Oracle's published licensing policies and audit practice since 2019.
Active Data Guard (Physical Standby, Open Read-Only Mode): The standby database is open for read-only queries while simultaneously receiving and applying redo from the primary. This mode — which allows reporting workloads to be offloaded to the standby — requires the Oracle Active Data Guard option, separately licensed in addition to Oracle Database Enterprise Edition. Active Data Guard is not available with Oracle Standard Edition 2.
The most common Oracle Data Guard licensing misconception we encounter in client assessments is the belief that a standby database used only for failover is "free" — requiring no Oracle Database licences. Oracle's published policy, enforced in LMS audits, is that standby databases require full Oracle Database licences. The question of how many licences depends on the configuration.
Standby Database Licensing Requirements
Oracle's licensing policy for standby databases has evolved — and become more restrictive — over time. The current Oracle position, as reflected in Oracle's Technology Licensing document and consistently enforced in LMS audits, is as follows.
Physical Standby in Mounted Mode
Oracle's current published position is that a physical standby database in mounted mode — not open for read or write — requires Oracle Database licences on the standby hardware. Oracle's reasoning is that the standby database software is installed and running (receiving and applying redo), even if it is not serving queries. The standby must be licensed at the same edition as the primary — if the primary runs Enterprise Edition, the standby must be Enterprise Edition.
In practice, Oracle has historically been more flexible on purely passive standbys used solely for disaster recovery — particularly where the standby is on different, less powerful hardware than the primary. However, Oracle's audit teams have increasingly applied strict licensing requirements to all standby configurations, and enterprises that rely on historical Oracle informal guidance rather than current published policy are taking audit risk.
Physical Standby Open Read-Only (Active Data Guard)
A physical standby opened in read-only mode — either for query offloading or for active reporting workloads — requires the Oracle Active Data Guard option. This option must be licensed on all processors where the standby is active, in addition to the Oracle Database Enterprise Edition base licence. Active Data Guard must also be licensed on the primary database's processors — because the primary's redo stream is the source enabling the standby's read-only capability.
Logical Standby
Oracle Logical Standby creates a standby database using SQL Apply rather than redo apply. Unlike physical standby, a logical standby is a fully open, separate Oracle Database that can accept read/write operations on non-replicated tables. A logical standby requires full Oracle Database Enterprise Edition licences on all standby processors — there is no special exception for logical standbys. If the logical standby uses any Oracle Database options (Partitioning, Diagnostics Pack, etc.), those options must also be licensed on the standby.
The Complete Data Guard Licence Matrix
The following matrix summarises the Oracle licensing requirements for the most common Data Guard configurations.
| Configuration | Oracle DB EE Required on Standby? | Active Data Guard Option Required? | Options Licences on Standby? |
|---|---|---|---|
| Physical standby — mounted, no read access | Yes (Oracle's current position) | No | If options used on primary: yes |
| Physical standby — open read-only (Active Data Guard) | Yes | Yes — on primary AND standby processors | Yes — all options in use on standby |
| Logical standby | Yes — full EE licence | No (Active Data Guard is not applicable) | Yes — all options in use on standby |
| Snapshot standby | Yes — full EE licence | Yes — Active Data Guard option required | Yes — all options in use |
| Far sync instance | Yes — EE licence on far sync host processors | No (far sync does not open the database) | No options required on far sync host |
Options Licensing on Standby Databases
One of the most frequently overlooked aspects of Data Guard licensing is the requirement to licence Oracle Database options on standby databases — not just on the primary. Oracle's policy is that any option in use on a standby database must be licensed on that standby's processors.
The practical challenge is that many Oracle Database options are in use on the primary database without enterprises being fully aware of it. Oracle's Diagnostics Pack and Tuning Pack are enabled by default in many Oracle Database configurations — and their automatic collection of performance metrics, which continues on the standby, triggers a licensing requirement for those options on the standby. Similarly, Partitioning — if enabled on the primary — is in use on the standby by virtue of the replicated data structures.
An independent assessment of which Oracle Database options are active on your primary database — and therefore must be licensed on your standby — is an essential precursor to any Data Guard licensing review. We regularly find that enterprises are paying to licence options on the primary that they do not need, and simultaneously not licensing options on the standby that Oracle's tools are actively using. See our guide to Oracle Database options: Oracle License Compliance: 10 Common Violations.
Reducing Your Data Guard Licensing Costs
Oracle Data Guard licensing costs can be substantial — particularly for enterprises with multiple standby databases, Active Data Guard configurations, or standbys on high-processor-count hardware. The following strategies are available for cost reduction.
- Right-size standby hardware. If your standby database is on the same hardware specification as the primary — identical processor count — you are paying the same Oracle licence cost for both. For pure DR standbys that will only be activated in a failover scenario, lower-processor-count standby hardware reduces the Oracle licence obligation on the standby. Oracle licences are based on the standby hardware's processors, not the primary's count. A standby on 2-processor hardware costs half the Oracle licences of an equivalent 4-processor standby.
- Eliminate unnecessary Active Data Guard usage. If your physical standby is opened in read-only mode for purposes other than active reporting — for example, for backup purposes, for RMAN restores, or simply because a configuration option was set incorrectly — and you are not actually using the read-only capability for user queries, removing the Active Data Guard option from the configuration eliminates its licence requirement. Active Data Guard at $23,000 per processor (list price) is a significant line item in any Data Guard configuration.
- Audit and remove unused Oracle Database options. Identify which Oracle Database options are actively used on your primary and standby databases — as distinct from which options are enabled or licensed. Disabling unused options (particularly Diagnostics Pack, Tuning Pack, and Partitioning) where they are not genuinely needed reduces both the primary and standby option licence cost. This exercise consistently delivers 15–30% option licence savings in enterprises that have not conducted a recent options review.
- Consider Oracle Maximum Availability Architecture (MAA) licensing alternatives. Oracle's Maximum Availability Architecture includes commercial models — including Oracle Exadata's licence terms — that may be more cost-effective for enterprises with large, high-availability Oracle estates. For some configurations, Exadata's all-inclusive licensing eliminates the need to separately licence Data Guard options.
- Negotiate standby licensing as part of the primary licence negotiation. Oracle's Data Guard licensing terms are not fixed in Oracle's published policies — they are subject to commercial negotiation. Enterprises negotiating primary Oracle Database licence agreements can and should negotiate standby database terms at the same time: reduced standby licence counts, free or discounted Active Data Guard, or contractually defined standby licensing methodologies. Once the primary agreement is signed, Oracle's leverage to offer standby concessions is significantly reduced.
Data Guard Audit Risk Areas
Oracle LMS audits of Data Guard configurations consistently identify the same categories of compliance exposure. Being aware of these risk areas allows enterprises to self-assess and remediate before Oracle initiates an audit.
Unlicensed Standby Databases
The most common finding is a standby database for which no Oracle Database licences have been purchased on the standby hardware. The enterprise purchased primary licences only, assuming the standby was implicitly included. Oracle's published policy is that standby licences are required, and Oracle's audit team will apply this policy regardless of the enterprise's historical understanding or any informal guidance received from Oracle account teams.
Active Data Guard Without the Option Licence
Oracle's LMS tools identify when a standby database is opened in read-only mode — a configuration that requires the Active Data Guard option. Enterprises that have configured Active Data Guard without purchasing the option licence consistently appear in Oracle LMS audit findings. The option licence cost, retroactively applied for multiple years plus support, produces substantial audit demands. See our full audit defence guide: Oracle Audit Defence: What to Do When You Get the Letter.
Options Active on Standby Without Standby Option Licences
Options such as Diagnostics Pack, Tuning Pack, and Partitioning — enabled on the primary and automatically active on the standby — create a licence requirement on the standby's processors that is frequently not met. Oracle's discovery tools identify active options on both primary and standby databases. Discrepancies between option licences purchased and option usage detected on standby hardware are a reliable Oracle LMS audit finding.
Related Resources
Back to the cluster pillar: The Complete Guide to Oracle Licensing & Contract Negotiation (2026).
Also in this cluster: Oracle Audit Defence Guide, Oracle License Compliance: 10 Common Violations, Oracle RAC Licensing Cost.
White papers: Oracle Negotiation Playbook · Vendor Audit Defence Handbook.
If you are unsure about your Oracle Data Guard licensing compliance position, our Vendor Audit Defence team provides independent assessment. Contact us for a confidential review.