Oracle Active Data Guard Licensing
- Separately licensed option for Oracle EE.
- Required if using real-time queries, fast incremental backups, or automatic block repair on standby databases.
- Both primary and standby databases require licensing.
- Licensing metrics (Processor or Named User Plus) must match the EE database.
- Passive standby without these features does not require an Active Data Guard license.
Oracle Active Data Guard Licensing
Oracle Active Data Guard (ADG) is an essential extension of Oracle Data Guard, providing additional capabilities such as real-time query on standby databases, incremental backups, and automatic data block repair.
Understanding its licensing requirements is crucial for compliance and cost-effective utilization.
Read more about Oracle Database Options licensing.
What Is Oracle Active Data Guard?
Oracle Active Data Guard builds upon the standard Oracle Data Guard technology, which is included with Oracle Database Enterprise Edition (EE). Data Guard provides basic disaster recovery capabilities, replicating data from a primary database to one or more standby databases.
Active Data Guard significantly enhances these capabilities, enabling standby databases to actively support real-time read-only workloads while still continuously applying redo data from the primary.
Key Capabilities of Active Data Guard:
- Real-time queries on physical standby databases without pausing redo application.
- Fast incremental backups from standby databases, reducing primary database load.
- Automatic block repair, repairing corrupted blocks automatically between primary and standby databases.
- Improved resource utilization, as standby databases simultaneously serve as disaster recovery and reporting environments.
Active Data Guard thus transforms standby databases into multi-functional assets, dramatically improving the value derived from infrastructure investments.
When Active Data Guard Licensing is Required
Active Data Guard is a separately licensed option from Oracle Enterprise Edition. It is mandatory whenever the specific features of Active Data Guard (like real-time querying or incremental backup offload) are actively used on standby databases.
Trigger Points for Licensing:
- Real-Time Query on Standby: Using the standby database to handle live queries while continuously applying redo logs.
- Incremental Backup from Standby: Performing fast incremental backups directly from the standby database.
- Automatic Block Repair: Actively using the auto-repair capabilities between primary and standby databases.
No additional licensing beyond EE is required if the standby is strictly passive—used only for disaster recovery and not actively queried.
Licensing Rules for Oracle Active Data Guard
Licensing Metrics:
Oracle Active Data Guard licensing follows the same metrics as your Oracle EE database:
- Processor-Based Licensing: Based on the number of processor cores in use.
- Named User Plus (NUP) Licensing: Based on the number of named users accessing the database.
The licensing metric chosen for Active Data Guard must match the metric used for the EE database license.
Processor Licensing Explained:
- If processor count licenses the primary database, you must license Active Data Guard by processor count for both the primary and standby databases.
- Each server’s processor cores involved (both primary and standby databases actively using ADG) must be licensed identically.
Example:
A company has a primary database with 32 processor cores. It deploys Active Data Guard functionality on one standby database server with 32 processor cores. To license Active Data Guard on each server, it must license 32 processor cores, resulting in total licenses for 64 processor cores.
Named User Plus Licensing Explained:
- If EE database licensing uses Named User Plus, the same users accessing the standby must be licensed for Active Data Guard.
- Typically, user counts are similar between primary and standby databases since the same users access both systems.
Minimum Licensing Requirement:
- Oracle’s standard minimum applies: 25 Named User Plus licenses per processor core.
Example:
If the primary and standby servers have four processors, a minimum of 100 Named User Plus licenses (4 processors x 25 NUP licenses per processor) would be required for Active Data Guard functionality.
Read about Oracle RAC One Node Licensing.
Practical Example of Active Data Guard Licensing
Consider the following practical scenario illustrating Active Data Guard licensing clearly:
Scenario Description:
- A retail company operates a high-transaction-volume database in its primary data center (primary database).
- A physical standby database resides in a second data center for disaster recovery.
- The company wants to offload intensive analytical reports from the primary to the standby, enabling real-time analytics without affecting the performance of the primary database.
Licensing Implications:
- The company triggers additional licensing requirements by enabling Active Data Guard to be on standby (real-time query capability).
- They license Active Data Guard using the Processor metric:
- Primary Database Server: 32 processor cores
- Standby Database Server: 32 processor cores
- The total Active Data Guard licensing requirement is 64 processor licenses (32 primary + 32 standby).
Operational Benefits:
- Real-time analytics queries are executed against up-to-date standby data.
- Nightly incremental backups are taken directly from the standby database, removing the backup I/O load from the primary.
- Automatic block repair capability provides data integrity and proactive corruption handling.
- Failover with minimal data loss if the primary fails.
Read about Oracle Partitioning Licensing.
Differentiating Active Data Guard from Regular Data Guard Licensing
Understanding when Active Data Guard licenses are needed compared to basic Data Guard functionality helps ensure compliance:
Regular Data Guard (Included in EE):
- Passive standby database, continuously applying redo logs.
- Not open simultaneously for queries or incremental backups.
- No additional licensing beyond EE.
Active Data Guard (Separate License):
- Enables real-time queries and incremental backups directly on standby.
- Must be licensed explicitly wherever Active Data Guard features are activated.
Common Licensing Misunderstandings for Active Data Guard
To avoid compliance issues, clarify common misconceptions around Active Data Guard licensing:
- Misunderstanding Standby Usage: Many believe that read-only queries on standby without real-time application are free. However, Active Data Guard licenses are required whenever simultaneous redo application and query capabilities are active.
- Partial Licensing Mistakes include licensing only the standby and ignoring the primary database (both primary and active standby require licensing when ADG features are used).
- Metric Mismatches: Mixing Processor-based licensing with Named User Plus licensing between primary and standby is prohibited.
Audit and Compliance Recommendations
Oracle actively audits licensing compliance, including Active Data Guard usage. To avoid penalties:
- Maintain Clear Documentation: Document clearly which standby databases have ADG enabled and the processors/users licensed.
- Regular Internal Reviews: Conduct periodic reviews to ensure licensing accurately reflects database operations.
- Seek Expert Advice: Engage Oracle licensing specialists when deploying or expanding Active Data Guard deployments.
Cost Optimization Strategies for Active Data Guard Licensing
Active Data Guard offers significant operational benefits but can increase licensing costs if not managed carefully.
Consider these strategies:
- Evaluate Standby Utilization: Clearly define whether Active Data Guard features are genuinely required. Passive standby databases may suffice, saving licensing costs.
- Consolidate Workloads: Limit Active Data Guard usage to fewer standby databases to minimize additional processor licenses.
- Optimize Hardware Choices: Carefully select hardware with processor configurations that minimize license counts (high-density core servers).
Comparing Active Data Guard and RAC for High Availability
Active Data Guard and Oracle Real Application Clusters (RAC) both enhance database availability but differ significantly:
Active Data Guard:
- Primarily focused on disaster recovery and reporting.
- Does not provide active-active workload balancing across multiple nodes.
- Typically lower licensing cost compared to RAC.
Real Application Clusters (RAC):
- Delivers active-active clustering for load balancing and high availability.
- Requires licensing on all nodes, typically at a higher overall cost.
- Suitable for continuous availability without performance degradation.
Choosing between Active Data Guard and RAC should align closely with business continuity needs and budget.
Key Summary Points for Active Data Guard Licensing:
- Active Data Guard is licensed separately from Oracle EE.
- Licensing is required for both primary and standby databases using ADG features.
- Licensing metrics (Processor or Named User Plus) must match the EE database licensing exactly.
- Regular Data Guard (passive standby) does not require separate ADG licensing.
- Real-time queries, incremental backups, or automatic block repair activate ADG licensing requirements.
Conclusion
Oracle Active Data Guard significantly enhances the value of standby databases, enabling real-time analytics, fast backups, and improved resilience. However, these capabilities require careful licensing management.
Understanding the licensing criteria, clearly documenting usage, and proactively managing compliance ensures organizations fully benefit from Active Data Guard without unexpected licensing risks or costs.
