Contents
Key takeawaysWhat Active Data Guard costsBasic vs Active Data GuardOptions on the standbyThe DR cluster trapChecking your standbysWhat we have seenWhat to do nextFAQActive Data Guard is a paid Enterprise Edition option, and the standby must carry the same licenses as production. Most of the money depends on whether the standby is licensed at all and whether it is ever read while redo apply runs.
- The option is the smaller number. Active Data Guard lists at $11,500 per processor plus 22 percent support, while the standby's own Enterprise Edition license lists at $47,500 per processor.
- It is licensed on both sides. Oracle requires the option on the primary and on every standby that uses an Active Data Guard feature.
- One state marks the line. A standby that V$DATABASE shows as READ ONLY WITH APPLY is using real time query, the core paid feature.
- Periodic reporting can stay free. Stopping apply, opening read only for the report window and then resuming apply stays inside basic Data Guard.
- Symmetry multiplies the standby. The standby needs every option production runs, such as Partitioning and the Diagnostics Pack, at each option's own rate.
- Shared DR clusters inflate the count. A standby on a shared virtualization cluster can count more processors than production under Oracle's partitioning position.
- Errors run in both directions. Check for open standbys without the option, and for mounted standbys carrying Active Data Guard they never use.
How is Oracle Active Data Guard licensed, and what does it cost?
Active Data Guard is an extra cost option on Oracle Database Enterprise Edition, listed at $11,500 per processor, plus 22 percent annual support, which is $2,530 per processor per year. Oracle's licensing manual requires it on the primary database and on every standby that uses one of its features, so a single primary and standby pair buys it twice.
Basic Data Guard is different. Redo apply, switchover, failover and snapshot standbys ship included with Enterprise Edition at no extra cost. Standard Edition 2 has no Data Guard at all, and a GoldenGate license includes Active Data Guard, which matters if you already own GoldenGate for replication.
Why is the standby usually a bigger bill than the option?
The standby server needs its own Enterprise Edition license at $47,500 per processor, counted on its own hardware and matched to production. That line exists whether or not you ever buy Active Data Guard. In most reviews the second Enterprise Edition license, and the options that follow it, cost far more than the option itself.
| Program | License | First year support at 22 percent | Needed on the standby when |
|---|---|---|---|
| Database Enterprise Edition | $47,500 | $10,450 | Always, for a physical standby receiving and applying redo |
| Active Data Guard | $11,500 | $2,530 | Any Active Data Guard feature is used, and then on the primary as well |
| Partitioning | $11,500 | $2,530 | Production runs it |
| Advanced Compression | $11,500 | $2,530 | Production runs it |
| Diagnostics Pack | $7,500 | $1,650 | Production runs it |
How to Negotiate an Oracle ULA: No Price List, Just Your Business Case
Where is the line between basic Data Guard and Active Data Guard?
The line is a standby open for reading while redo apply runs. V$DATABASE reports that state in the OPEN_MODE column as READ ONLY WITH APPLY, and it is the core Active Data Guard entitlement, which Oracle calls real time query. A mounted standby, or one open read only with apply stopped, stays inside basic Data Guard.
Oracle's Data Guard documentation states that without the option, redo apply must be stopped before any standby instance is opened. The rest of the Active Data Guard feature list sits on the same side of the line, as the table shows.
| Capability | Basic Data Guard, included with Enterprise Edition | Active Data Guard option |
|---|---|---|
| Redo apply to a physical standby | Included | Included |
| Switchover and failover | Included | Included |
| Snapshot standby, backups taken from a mounted standby | Included | Included |
| Standby open read only, apply stopped | Included, the periodic reporting rule | Included |
| Standby CDB root open read only while apply runs, with every PDB closed | Included | Included |
| Standby open read only while apply runs | Not included, this is the line itself | The core entitlement: real time query |
| Automatic block repair, far sync, standby block change tracking | Not included | Included |
| Real time cascade, Global Data Services, Application Continuity | Not included | Included |
| Rolling upgrade with DBMS_ROLLING, DML redirection | Not included | Included |
Do backups from the standby need the option?
Backups from a mounted standby are free. Fast incremental backups are not, because block change tracking on a physical standby is an Active Data Guard feature.
The exception is Zero Data Loss Recovery Appliance. If you back up the standby to ZDLRA, fast incremental backup and real time cascade need no option license, provided no other Active Data Guard feature is in use.
How does the free reporting lane work in practice?
Basic Data Guard allows you to open a physical standby for reports as long as apply is paused for the whole window. The sequence below is the one we ask DBAs to write into the runbook, so the free lane is a documented procedure that anyone on call can follow.
- Stop redo apply with ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL, or set the standby to APPLY-OFF in the Data Guard broker.
- Open the standby read only and confirm V$DATABASE shows READ ONLY, not READ ONLY WITH APPLY.
- Run the reporting window.
- Shut the standby down and restart it in MOUNT mode. Without the option, an open instance must be closed before apply restarts.
- Start apply again and log the window's start and end times.
Redo keeps shipping and archiving while apply is paused, so you lose no data. You do build an apply backlog, and a failover in that window must apply it before the standby opens. Size the reporting window against your recovery time objective.
We see both errors. Some companies pay for real time query to run a nightly batch report, and others run live dashboards on basic entitlements. An audit reads V$DATABASE either way.
Oracle Database Options and Packs Guide
Every Enterprise Edition option and pack, what triggers it and how to remediate without paying list price.
Get the white paper →Which licenses does a Data Guard standby have to carry?
A physical standby must carry the same licenses as production: Enterprise Edition on the standby hardware's own processor count, and every option whose redo it applies, such as Partitioning, Advanced Compression and the management packs, each at its own rate. This is how four figure option decisions on production become six figure standby bills.
Option symmetry turns a modest DR decision into the second largest line in many Oracle contracts. Our DR licensing analysis covers the failover windows and the ten day rule that bound the exceptions. Snapshot standbys, mounted backups and switchover add nothing to the Active Data Guard bill, because each one keeps the standby closed to readers while apply runs.
What does a standby cost on one 16 core server?
Say production runs on a two socket Intel Xeon server with 8 cores per socket. At Oracle's 0.5 core factor, 16 cores count as 8 processors. Production uses Partitioning and the Diagnostics Pack, and the standby sits on identical hardware. At list price, before any discount, the standby looks like this.
| Line | Calculation | License | Annual support |
|---|---|---|---|
| Enterprise Edition on the standby | 8 x $47,500 | $380,000 | $83,600 |
| Partitioning on the standby | 8 x $11,500 | $92,000 | $20,240 |
| Diagnostics Pack on the standby | 8 x $7,500 | $60,000 | $13,200 |
| Standby subtotal, basic Data Guard | $532,000 | $117,040 | |
| Active Data Guard, standby and primary | 16 x $11,500 | $184,000 | $40,480 |
| Total if you run real time query | $716,000 | $157,520 |
A discount lowers every line by roughly the same share, so the proportions hold. The option is about a quarter of the spend, and the standby's own stack is the rest. If the reporting need is a nightly extract, the free lane removes the $184,000 line entirely.
Should you buy Active Data Guard so the standby earns its keep?
Oracle's account teams, and many DBAs, argue that an idle standby is wasted money and that real time query puts it to work. We disagree when the reporting need is periodic. The option is priced on the primary as well as the standby, so the idle hardware argument counts only half the cost.
Buy it when users need current data during the day, or when you need automatic block repair or far sync. Use the free lane for everything else.
Why can a standby count more processors than production?
It happens when the standby runs on a shared virtualization cluster at the DR site. Oracle's partitioning position counts every core the standby could run on, which means the whole cluster rather than the pinned VM. The DR site is then the part of the contract least prepared for the virtualization licensing arithmetic.
DR sites invite consolidation because the hardware is sized for a disaster that has not happened. Take the 8 processor production server from the worked example, and put its standby on a four host DR cluster where each host has two 16 core sockets. That is 128 cores, or 64 processors, eight times production's count.
- Enterprise Edition alone. 64 x $47,500 is $3,040,000 at list.
- With the matching options. Adding Partitioning and the Diagnostics Pack takes the per processor stack to $66,500, and the total to $4,256,000.
- On a dedicated host. The same standby costs $532,000, as the table above shows.
How do you keep the standby's count at its own hardware?
The defenses are the standard ones, and they cost least when they are built into the DR design before any audit prices the cluster.
- Dedicated DR hosts. A physical server, or a small cluster that runs only Oracle, sized for the standbys it holds.
- Approved hard partitioning. Technologies Oracle lists as hard partitions limit the count; our hard partitioning guide covers the setup and the evidence.
- A paper trail for the cluster boundary. Host affinity rules, vCenter and storage separation, and change records that show the standby could not move. The vMotion and DRS argument is where most disputes land.
- A design review before the build. Check the DR design with licensing in the room before anyone approves the hardware order.
How do you check whether a standby is using Active Data Guard?
Query each standby and the primary directly. The views below show the open state and the feature usage Oracle's audit scripts read, so you see the same evidence LMS would. Run them quarterly and after every DR test or upgrade.
| Where | What to run | What it tells you |
|---|---|---|
| Each standby | SELECT open_mode FROM V$DATABASE | READ ONLY WITH APPLY means real time query is in use now |
| Each standby, multitenant | SELECT name, open_mode FROM V$PDBS | Any PDB open for reads while apply runs needs the option; the root alone does not |
| Each standby | SELECT status FROM V$BLOCK_CHANGE_TRACKING | ENABLED means fast incremental backup, an Active Data Guard feature unless you back up to ZDLRA |
| Primary | SELECT * FROM V$DATAGUARD_CONFIG | Lists every member of the configuration, including any far sync instance |
| Primary and standby | DBA_FEATURE_USAGE_STATISTICS, rows such as Active Data Guard - Real-Time Query on Physical Standby | Detected usage with first and last usage dates, the history an auditor will ask about |
Read the results with the same script output discipline you apply to every other option, and price any gap against the price list in both directions. Our guide to the feature usage report shows how to run that review before Oracle's script does.
Can you stop a standby from opening with apply running?
Partly. The broker's APPLY-OFF state and a written runbook handle planned reporting.
Some DBAs also set the undocumented parameter _query_on_physical to FALSE so the database refuses to open for reads while apply runs. Hidden parameters are unsupported unless Oracle Support approves them, so ask Support first and keep the runbook as the main control.
What have we seen in recent Active Data Guard reviews?
Across roughly 30 to 40 Oracle Database environments I reviewed between 2024 and 2026, the standby drove the cost far more often than the option did. In about 6 in 10 of those environments the DR standby was not correctly licensed, and the errors ran in both directions.
- Underlicensed. The most common single finding was a standby open for reading with apply running and no Active Data Guard on the contract, with V$DATABASE holding the evidence.
- Overlicensed. Full production stacks, including Active Data Guard, bought for standbys that only ever mounted, took backups and waited. The free rules already covered what those standbys did.
The second group deserves as much attention as the first. A mounted standby on basic Data Guard needs its Enterprise Edition and matching options, but the Active Data Guard line on it pays for a feature no one uses. That support is money you can recover at the next renewal.
A standby that only mounts, backs up and waits needs Enterprise Edition. It does not need Active Data Guard.
What will Oracle's account team say, and how should you answer?
- "Feature usage shows Active Data Guard, so you owe it on every processor of every database in the configuration." Ask for the first and last usage dates per database. Oracle's own rule covers the primary and the standbys that used the features; other standbys in the configuration do not need the option.
- "Your standby sits on the DR VMware cluster, so every host in it needs licensing." Oracle's partitioning policy states that it is for educational purposes and does not form part of your contract. Ask which clause of your agreement they rely on, and bring the cluster boundary evidence.
- "Active Data Guard makes your DR hardware pay for itself." Ask for the price on both the primary and the standby, then compare it with running the same reports in the free lane.
Which mistakes cost the most?
- Opening the standby during a DR test with apply running. Feature usage keeps the first and last dates, so one test can start an audit conversation.
- Running a DBMS_ROLLING upgrade. Rolling upgrade with Active Data Guard is on the option's feature list, and upgrade projects rarely check.
- Adding a far sync instance for zero data loss at distance. Far sync is part of the option, however small the instance is.
- Turning on block change tracking for faster standby backups. Unless the backups go to ZDLRA, that counts as Active Data Guard usage.
What to do next
- This quarter. Query V$DATABASE on every standby, and V$PDBS on multitenant ones, and compare the open mode with what the contract says. READ ONLY WITH APPLY is both the finding and the evidence.
- Write the free lane into the runbook. Apply stopped, open read only for the reporting window, restart in mount, apply resumed, with the times logged.
- License the symmetry or break it. The standby carries production's options, so every option added to production is on the standby's bill too. Check both before approving new option use.
- Price Active Data Guard on both sides. If real time query is justified, license the primary and each standby that uses it, and leave standbys that only mount off the order.
- Fix the DR cluster boundary at design time. Use dedicated hosts or approved hard partitioning, with the paper trail, before the standby outcounts production.
- Review the overspend direction before renewal. Mounted standbys carrying Active Data Guard are support you can stop paying for. The Oracle practice reviews standby licensing with you in both directions.
Frequently asked questions
How is Oracle Active Data Guard licensed?
Per processor or per Named User Plus, as an extra cost option on Enterprise Edition. The processor price is $11,500 plus 22 percent support. It sits on top of the standby's own Enterprise Edition license, which matches production option for option, while basic Data Guard with redo apply, switchover, failover and snapshot standbys comes with Enterprise Edition.
When does a standby need the Active Data Guard option?
As soon as it is read while redo apply runs, the state V$DATABASE reports as read only with apply. Using automatic block repair, far sync or block change tracking on the standby also requires the option. A standby kept mounted, or opened only after apply is paused, does not.
Can we run reports on a standby without Active Data Guard?
Yes, if apply is paused for the whole report window. Stop apply, open the standby read only, run the reports, return it to mount and restart apply. Batch and overnight reporting fits this pattern well; dashboards that need current data during the working day do not, and those need the option.
Does the standby need the same options as production?
Yes. A standby applying redo from a production database that runs Partitioning or the Diagnostics Pack needs those options too, each at its own rate. That symmetry rule, more than the Active Data Guard price, is why a standby often becomes a six figure line.
Why might a standby count more processors than production?
Because of the DR cluster trap. When the standby VM runs on a shared virtualization cluster, Oracle's partitioning position counts every core in that cluster instead of the VM's allocation. Dedicated DR hosts, or documented affinity decided when the site is designed, keep the count at the standby's 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. It was the leading single finding across our reviews, and in 6 in 10 of the environments we reviewed the DR standby was licensed incorrectly in one direction or the other. A quarterly check of each standby's open mode against the entitlement catches it early.
Does Active Data Guard have to be licensed on the primary database too?
Yes. Oracle's licensing manual requires the option on the primary as well as on any standby using its features. Additional standbys in the same configuration that use none of those features do not need it, so a third, mounted standby can stay on basic Data Guard.
What does Active Data Guard cost per Named User Plus?
It lists at $230 per Named User Plus, with $50.60 a year in support. The Enterprise Edition minimum of 25 Named User Plus per processor applies to the option as well, so on small user counts the minimum usually sets the price.