Oracle Active Data Guard. Licensed the buyer side way.

Active Data Guard is the read only, real time apply, automatic block repair extension of basic Data Guard. Basic Data Guard ships free with Enterprise Edition. Active Data Guard is a separately licensed option.

The option price runs at twenty three thousand dollars per processor list. The standby server carries a full Enterprise Edition license plus the Active Data Guard option, matching the primary. Failover server exceptions are narrow and rarely apply.

Read this alongside the Oracle knowledge hub, the Database 23ai guide, the ULA framework, the Oracle services page, and the Vendor Shield subscription.

What Active Data Guard is

Active Data Guard is the licensed Enterprise Edition option that adds three capabilities on top of basic Data Guard. Each capability has a contractual trigger.

The three triggers

• Open read on the standby. Any query, report, or BI workload reading the standby triggers ADG licensing.
• Real time query. Real time apply combined with open read mode equals an ADG workload.
• Automatic block repair. Standby healing a corrupt block on the primary requires ADG.

Additional features that require ADG

• Far sync instance. Cascading standby across a wide area network.
• Standby block change tracking. Incremental RMAN backup off the standby.
• Application continuity on standby. Session draining and replay on failover events.
• Global Data Services with read scaling. Load balancing reads across multiple standbys.

The licensing metric

Active Data Guard licenses on the same metric as the underlying Database Enterprise Edition. Processor or Named User Plus. The processor metric uses the Oracle Core Factor Table.

Processor metric math

1. Count physical cores. On the standby server, count every CPU core inside the database fence.
2. Apply the core factor. Intel Xeon, AMD EPYC sit at 0.5. Power and Itanium use a higher factor.
3. Round up to the next whole processor. Oracle does not pro rate fractional processors.
4. Match Enterprise Edition. ADG always rides on top of EE, never alone.

Named User Plus alternative

• Minimum twenty five Named User Plus per processor. Oracle floors the count regardless of actual users.
• Counts every authorized human and device. Internal staff, contractors, and non human devices that query the standby.
• Generally uneconomical at scale. Most ADG estates default to the processor metric.

Standby server posture

Oracle requires a full Enterprise Edition license on the standby server, matching the primary. Active Data Guard adds the option license on top. The standby is not a free passive copy.

The one to one equivalence rule

• Same edition. Enterprise Edition on the primary, Enterprise Edition on the standby.
• Same metric. Processor on the primary, processor on the standby.
• Same options. Every option used on the primary licensed on the standby.
• Same core count or higher. Standby can over provision; cannot run under.

The narrow ten day failover rule

Oracle allows a single cold failover server up to ten calendar days per year without a license. The rule sits inside the Oracle Master Agreement and the partitioning policy. The criteria are strict.

• Same cluster or storage array. The failover node must share storage with the primary.
• Cold state only. The instance stays shut down until the failover event.
• Maximum ten days per year. Combined across all failover events.
• Single backup node only. Multiple cold standbys exit the exception.

Option stacking math

Active Data Guard rides on top of Enterprise Edition and stacks alongside the other Database options. The stacking math drives the per processor cost on every standby node.

Stacked cost per processor on a typical estate

License component	List per processor (USD)	Required on standby	Notes
Enterprise Edition	47,500	Yes	Base license
Active Data Guard	23,000	Yes	Adds open read and block repair
Partitioning	11,500	If used on primary	Most Oracle estates use it
Advanced Compression	11,500	If used on primary	OLTP and backup compression
Diagnostics Pack	7,500	If used on primary	AWR and ASH
Tuning Pack	5,000	If used on primary	SQL tuning advisor
Real Application Clusters	23,000	If clustered standby	Per node, both primary and standby

Discount benchmarks

• Active Data Guard option. Forty to seventy percent off list is the buyer side range.
• Enterprise Edition. Sixty to seventy five percent off at processor volume.
• Renewal uplift. Contractual eight percent default applies to support, not new licenses.
• Cloud BYOL credit. Same option price applies; cloud move does not unlock new discount.

Audit traps and pitfalls

Oracle License Management Services targets ADG deployments because the standby license posture is widely misunderstood. Five traps catch most enterprises during an audit.

Five common ADG audit traps

1. Standby missing the option. Primary licensed for ADG, standby licensed only for EE.
2. Read replica on standby. Reporting workload pointed at the standby without ADG license.
3. Cold standby running hot. Ten day exception claimed on a continuously applying standby.
4. RMAN backup off standby. Standby block change tracking requires ADG, often unlicensed.
5. Cloud BYOL miscount. Customer counts vCPU instead of physical cores under the Authorized Cloud Environment rules.

Buyer side defense moves

• Document the standby posture. One pager confirming role, mode, and apply state.
• Lock down read access. No SELECT, no application, no reporting tool on the standby unless licensed.
• Run the options scan. DBA_FEATURE_USAGE_STATISTICS exposes Active Data Guard usage automatically.
• Pre price the gap. Calculate the cost of clean licensing before Oracle quotes audit settlement.
• Engage independent advisor. Pre audit position discovery beats reactive defense.

What to do next

The seven step buyer side checklist below puts the Active Data Guard estate on a clean licensing footing before the next Oracle renewal or audit conversation.

1. Inventory every standby. Physical, virtual, cloud BYOL, and far sync instances.
2. Run the feature usage scan. DBA_FEATURE_USAGE_STATISTICS plus options scan output.
3. Map reads to standbys. Application, reporting, BI, ETL connections.
4. Reconcile the option count. Primary plus standby, matched one to one.
5. Identify the cold standby candidates. Strict ten day rule criteria.
6. Pre price the gap. Use the stacked cost per processor table.
7. Open the conversation with Oracle. On documented data, not on the auditor's spreadsheet.

Frequently asked questions

How Redress engages on Oracle strategy

Redress runs Oracle advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment.

Read the related benchmarking page, the about us page, the locations page, and the contact page.