Oracle Data Guard — the technology that keeps a standby database synchronised with a primary database for disaster recovery and failover — is included in Oracle Database Enterprise Edition at no additional cost. Oracle Active Data Guard — which adds the capability to query that standby database while it is in managed recovery mode, and use it for reporting, backups, and rolling upgrades — is a separately licensed option at $23,000 per processor. The compliance trap is that the line between "included Data Guard" and "licensed Active Data Guard" is not where most DBAs think it is. Opening a standby database for any read-only access — including a single test SELECT statement — while it is in managed recovery mode activates Active Data Guard and triggers the licence requirement. Former Oracle insiders explain exactly where the line is, how Oracle detects it, and how to defend your DR environment against inflated Active Data Guard audit claims.
Oracle Data Guard is Oracle's high-availability and disaster recovery framework for Oracle Database Enterprise Edition. It maintains one or more standby databases as transactionally consistent copies of the primary database, continuously applying redo log data from the primary to keep standby databases synchronised. Data Guard is included in Oracle Database EE — there is no additional licence cost for the base Data Guard capability.
The included Data Guard capabilities are:
The critical point: a standby database in managed recovery mode (applying redo, mounted but not open) is fully covered by the included Data Guard capability. No additional licence is required to maintain, switchover to, or fail over to a physical standby database that is in MRP (Managed Recovery Process) mode.
Oracle Active Data Guard extends the base Data Guard capability in ways that allow the standby database to serve workloads while simultaneously applying redo from the primary. This is the fundamental distinction: included Data Guard keeps the standby database available for failover but not actively serving workloads while in managed recovery; Active Data Guard makes the standby database simultaneously a recovery target AND an active, queryable database instance.
The features that require an Active Data Guard licence are:
The licensing boundary between included Data Guard and the separately licensed Active Data Guard Option is precisely defined — and more strict than most DBAs realise. The trigger for Active Data Guard is opening the physical standby database in READ ONLY mode while managed recovery (redo apply) is active. Not the duration of the open state. Not the volume of queries executed. The trigger is the act of opening the standby for reads while redo apply is running.
The command that crosses the line is:
This is in contrast to the commands that remain within the included Data Guard boundary:
The included Data Guard allows you to open a physical standby for read-only access after stopping the managed recovery process. The standby database will be open and queryable, but it will not be applying redo from the primary during that period. This is the "manually managed" read-only standby model — it requires operational discipline (stopping and restarting MRP to open and close the standby) but is fully compliant without ADG.
The One-Query Trap: A DBA who opens a physical standby READ ONLY while MRP is running — even for a single test query to verify standby data currency — has triggered an Active Data Guard licence requirement that Oracle's dba_feature_usage_statistics will record. The feature usage entry includes the first date this occurred, and Oracle's LMS audit claim will be backdated to that first usage date. Ensure DBAs understand the ADG licence boundary before any read access to standby databases.
Our Oracle Compliance Review audits your Data Guard configuration, standby open history, and dba_feature_usage_statistics across your estate — identifying any Active Data Guard usage before it surfaces in an Oracle audit.
Oracle Active Data Guard is priced at $23,000 per processor (perpetual list) on the same Processor metric as Oracle Database EE. Annual support is approximately $5,060 per processor at Oracle's 22% support rate. Active Data Guard must be licensed for each processor on the standby database server — not just the primary database server.
This is a frequently misunderstood point: the Active Data Guard licence is required for the standby database host, not the primary. The logic is that ADG provides active workload-serving capability to the standby host, so the standby host processors are what Oracle licences. However, in practice most enterprises also require the ADG licence on the primary host to cover features like Automatic Block Repair and Lost Write Protection, which operate on both sides of the Data Guard configuration.
For organisations running Oracle Database EE in active-passive DR configurations with physical standby databases, the ADG licence cost for the standby environment represents approximately 48% of the Oracle Database EE licence cost for the same processor count ($23,000 vs $47,500 per processor). This is a significant cost that Oracle's sales teams frequently omit from initial DR architecture discussions — the "Oracle provides Data Guard for free with EE" message omits the ADG licence requirement for operational standby query workloads.
Oracle's LMS audit scripts detect Active Data Guard usage through multiple data dictionary views on both the primary and standby databases. The detection is comprehensive and historically retroactive:
The FIRST_USAGE_DATE in dba_feature_usage_statistics is Oracle's primary evidence source for ADG audit claims. This date reflects the first time the standby's open mode included active redo apply — which in many environments occurred years before the organisation knew ADG required a separate licence. Oracle's standard LMS audit demand includes ADG licence cost from FIRST_USAGE_DATE to the date of audit settlement.
Beyond Active Data Guard specifically, Oracle's licensing rules for DR environments more broadly are a source of ongoing commercial tension. Oracle's published policy is that standby databases in a Data Guard configuration — even those used purely for DR purposes — must be fully licensed for Oracle Database EE. There is no DR discount, no passive-server discount, and no provision for lower-cost standby licences in standard Oracle agreements.
This means a four-processor production Oracle EE database with a four-processor physical standby requires eight processor licences of Oracle Database EE (four for primary, four for standby) even though the standby server never serves production workloads. The cost: 8 processors × $47,500 = $380,000 in perpetual licences. Annual support: $380,000 × 22% = $83,600.
Some Oracle Enterprise Agreements and ULA structures include language that modifies the DR standby licensing requirement — for example, allowing one passive standby database to be maintained without additional licence cost, or licensing the DR standby environment at a reduced rate. These contractual provisions must be explicitly negotiated. Oracle's standard terms do not include them. Our Oracle Contract Negotiation advisory consistently includes DR standby licence terms as a key negotiation objective in EA and ULA structures — enterprises that negotiate these terms save $100,000–$500,000+ in standby environment licence costs over the life of the agreement.
The "10 Days per Year" Rule — What It Doesn't Cover: Some DBAs believe Oracle allows standby databases to be used for up to 10 days per year for testing without requiring full licensing. This rule is specific to very limited testing scenarios and does not apply to operational Data Guard standby databases. Do not rely on the 10-day rule for production DR environments. Review your Master Agreement and Technical Support Policies for the specific terms that govern your deployment.
Based on our experience in Oracle DR environment compliance reviews, the most frequent Active Data Guard compliance gaps arise from:
Our Oracle Audit Defence team reviews ADG usage history, challenges FIRST_USAGE_DATE claims, and analyses your Master Agreement DR terms to establish a defensible position against Oracle's ADG audit demand.
Active Data Guard audit claims are defendable on several grounds, and the best outcomes come from combining technical challenges to Oracle's usage evidence with contractual analysis of your DR licensing terms:
FIRST_USAGE_DATE challenge: Oracle's ADG licence claim is backdated to the FIRST_USAGE_DATE in dba_feature_usage_statistics. If this date reflects a brief, inadvertent ADG usage event — say, a DBA who opened the standby READ ONLY WITH APPLY for 30 seconds during a DR test and then reverted to MRP-only mode — the duration and functional impact of that usage can be challenged in settlement negotiations. Oracle's claim that a 30-second inadvertent activation triggers years of back-licensing from that date is commercially disproportionate and negotiable.
DR testing vs production use: If ADG usage occurred exclusively during scheduled DR tests — not as a continuous production read workload — this limits the functional benefit Oracle can demonstrate for the back-licence claim. Oracle's licence obligation arises when the feature is used, but the commercial settlement value of brief test usage is significantly lower than continuous production reporting workloads.
Contract term analysis: Review your Master Agreement, ULA certification report (if applicable), and EA Order Forms for any provisions relating to standby database licensing or DR environment terms. Some agreements explicitly limit Oracle's right to assert ADG back-licensing for certain DR test scenarios.
The Healthcare: Compliance Remediation case study included an Active Data Guard component where Oracle's initial ADG back-licence claim was based on a FIRST_USAGE_DATE from DR testing activities three years prior. Our defence team demonstrated that the usage was exclusively during annual DR tests (four occurrences over three years, each for less than two hours), and negotiated the settlement to cover only the test periods rather than three years of continuous ADG usage at the full licence rate. The settlement was $84,000 versus Oracle's initial demand of $690,000.
Engage our Oracle Audit Defence service or our Oracle Compliance Review to establish your ADG position before Oracle's LMS team formalises the audit claim. Proactive review of your standby database configurations — and correcting any inadvertent ADG activations — before an audit notification is always the most cost-effective approach.
Comprehensive guide to Oracle Database EE, Data Guard, Active Data Guard, RAC, and all separately licensed options — including the DR environment licensing rules, compliance methodology, and audit defence framework.
Download Free Guide →Active Data Guard audit activity has increased significantly as Oracle's LMS team targets DR environments. Our newsletter tracks Oracle Data Guard and ADG compliance developments for enterprise buyers.
Oracle Licensing Experts Team — Former Oracle executives, LMS auditors, and contract managers with 25+ years of Oracle licensing experience, now working exclusively on the buyer side. Not affiliated with Oracle Corporation. Learn about our team →
Free Research
Download our Oracle OCI Licensing Guide — expert analysis from former Oracle insiders, 100% buyer-side.
Download the OCI Licensing Guide →