Data Guard versus Active Data Guard.
The single most important distinction in this topic is the one Oracle's own naming makes easy to miss. Basic Data Guard is included in Oracle Database Enterprise Edition at no extra licence cost. It maintains a physical standby database that receives changes from the primary and stands ready to take over if the primary fails. Active Data Guard is a separately licensed option that adds capabilities on top of basic Data Guard, most notably the ability to open the standby for read only queries while it continues to apply changes. The free version keeps the standby mounted and closed. The chargeable version lets you read from it. That one capability is the difference between a feature that costs nothing and one that carries a per processor licence on every server it touches. We sit on the buyer side and this distinction is where most exposure begins.
How Active Data Guard is priced.
Active Data Guard is licensed as a per processor option, or per named user plus, on the same processor metric as the Enterprise Edition database underneath it. It must be licensed on both the primary and the standby servers, because the feature is in use across the configuration, not only on the standby. This doubling effect surprises buyers who assume the standby is a passive insurance copy. If you license the primary and then enable read only access on a standby of equal size, you have effectively doubled the option cost. The metric follows the hardware on both sides of the configuration. Understanding this is the foundation for controlling it, and it sits alongside the wider option economics we explain on our database licensing deal type page.
Active Data Guard cost control checklist
- Confirm whether you need read access on the standby or only failover.
- Remember basic Data Guard failover is free in Enterprise Edition.
- Account for the option on both primary and standby processors.
- Check whether features were enabled by default during setup.
- Right size the standby so the option cost is not doubled needlessly.
- Quantify the exposure before any Oracle review does.
The standby trap.
The most common and costly mistake is enabling Active Data Guard features without a deliberate licensing decision. A team builds a standby for disaster recovery, which needs only the free basic Data Guard. Then someone opens the standby for reporting to offload queries from the primary, a natural and useful thing to do, and in that moment the configuration begins using the chargeable option. Nobody bought a licence, the technical change felt minor, and the obligation now attaches to every processor on the standby. Oracle's review tooling captures the read only open events, and the finding lands as a compliance gap priced across the standby hardware. The buyer side response is to govern who can open a standby, to treat read access as a licensing decision and not a technical convenience, and to establish your true usage before an audit does. We cover the audit mechanics in our database audit defense article.
When the option is worth it.
Active Data Guard is a genuinely valuable capability when you need to run reporting against a current copy of production, when you require very high data protection guarantees, or when offloading read traffic materially improves the primary. The buyer side position is not that the option is never worth buying, it is that it should be a deliberate, priced decision rather than an accidental one. If the workload truly needs read access on the standby, the right move is to negotiate the option into a renewal or new purchase where it attracts the same discount as the rest of the estate. If failover protection is all you need, basic Data Guard delivers it for free and the option should never be enabled. Our cloud migration advisory service regularly redesigns high availability architectures to match the genuine requirement rather than the default configuration.
Negotiating the option.
If you need Active Data Guard, price it inside a larger commercial conversation and never settle it as an isolated audit finding. Options carry the same discount potential as the base database, so folding the requirement into a renewal or new licence purchase gives you the leverage of the whole deal. An option surfaced under audit pressure is priced at or near list and often back dated with support. The same option negotiated as part of a forward agreement is routinely discounted alongside everything else. The discipline is to surface your option requirements yourself, on your timeline, rather than letting Oracle surface them on theirs. Our renewal negotiation service inventories every database option before the conversation with Oracle begins.
Holding the line.
Active Data Guard exposure is controllable with one habit: treat the line between standby failover and standby read access as a licensing boundary, not a technical detail. Know whether you genuinely need to read from the standby, govern who can open it, account for the option on both servers, and never accept a finding as a settled liability. Where only failover is required, the free basic Data Guard does the job. Where read access is genuinely needed, negotiate the option deliberately and at discount. Bring an independent assessment in before Oracle establishes your position for you. The product is covered on our Oracle Database product page, the full picture is in our database negotiation pillar guide, and any standby configuration should be checked in a contract review.
Related resources.
- Database Negotiation pillar guide
- Renewal Negotiation service
- Cloud Migration Advisory service
- Database Licensing deal type page
- Oracle Database product page
- Oracle Audit Defense Handbook 52 page reference paper.
- Partitioning Option Pricing related sub article.