Oracle Goldengate Licensing Guide

How Oracle GoldenGate licensing works:

• Oracle Goldengate can be licensed under the named user, license, and processor metric.
• You must license both the source and target hosts.

Oracle Goldengate Licensing

Oracle GoldenGate is a powerful software solution widely used for data replication, real-time integration, synchronization, and disaster recovery across diverse IT environments.

While Oracle GoldenGate delivers significant operational benefits, its licensing complexity often creates confusion, compliance risks, and unexpected organizational costs. Understanding Oracle GoldenGate’s licensing rules, models, metrics, and restrictions is crucial to effective deployment and cost optimization.

This detailed Oracle GoldenGate licensing guide clearly explains Oracle’s licensing approach for GoldenGate, including licensing models, processor-based licensing calculations, license restrictions, common pitfalls, practical examples, best practices, and strategic recommendations to help your organization manage licensing efficiently and remain compliant.

Oracle GoldenGate Licensing Basics

Oracle GoldenGate is primarily licensed using Oracle’s standard software licensing metric—Processor-based. Unlike some Oracle products that offer Named User licenses, Oracle GoldenGate typically requires processor licensing directly tied to server hardware or virtual CPUs.

Organizations must clearly understand how Oracle calculates processor licenses for GoldenGate deployments, as misinterpretations frequently result in compliance violations during Oracle audits.

Oracle GoldenGate Licensing Metrics Explained

Oracle GoldenGate licensing is primarily based on Processor licensing, which calculates license entitlements according to the number of processors or cores in the servers running the GoldenGate software. Oracle typically uses the following licensing rules and calculations for GoldenGate:

Processor Licensing Model

Oracle Processor licenses for GoldenGate are determined by the total number of physical processor cores multiplied by Oracle’s defined Core Factor. Oracle maintains a standardized Core Factor Table for this purpose, which assigns licensing multipliers to different types of processors.

Oracle Core Factor Table Examples:

Organizations must carefully apply these core factors to accurately calculate the required GoldenGate processor licenses.

Practical Example – GoldenGate Processor Licensing Calculation:

• A customer deploys Oracle GoldenGate on a server with two Intel Xeon CPUs, each having 8 cores (16 total cores).
• The Oracle core factor for Intel Xeon CPUs is 0.5.
• Required processor licenses: 16 cores × 0.5 = 8 Oracle GoldenGate Processor licenses.

Oracle GoldenGate Licensing for Virtualized Environments

GoldenGate deployments in virtualized environments (such as VMware or Oracle VM) add complexity to license management and require clear understanding:

• Oracle typically mandates licensing all physical processors within a virtualized cluster if GoldenGate is installed on any virtual machine.
• Oracle licensing for VMware often requires all hosts in a VMware cluster running Oracle GoldenGate instances to be fully licensed, irrespective of actual VM allocation.

VMware Licensing Scenario Example:

• VMware cluster with three physical servers, each containing two Intel Xeon CPUs (48 cores in total across the cluster).
• Oracle GoldenGate runs on one VM assigned to only 4 virtual CPUs (vCPUs).
• Oracle licensing rules typically require licensing the entire physical cluster (48 cores × 0.5 core factor = 24 processor licenses required), despite minimal VM allocation.

Oracle GoldenGate Licensing in Cloud Environments

When deploying GoldenGate on public cloud services (AWS, Azure, or Oracle Cloud Infrastructure), Oracle uses specific licensing models:

AWS and Azure Licensing Rules for GoldenGate:

• Licensing is based on virtual CPUs (vCPUs).
• Oracle calculates licenses at a fixed rate of two vCPUs equal to one processor license (2:1 ratio).
• The Oracle Core Factor Table does not apply in cloud environments.

Practical Example – AWS Licensing Calculation:

• GoldenGate was deployed on an AWS EC2 instance with 16 vCPUs.
• Required Oracle licenses: 16 vCPUs ÷ 2 = 8 Processor licenses.

Oracle Cloud Infrastructure (OCI) Licensing:

• Oracle offers GoldenGate as a cloud subscription service (managed) or through Bring Your Own License (BYOL).
• Under BYOL, licensing calculations are similar to AWS/Azure (2 vCPUs = 1 processor license).

Common Oracle GoldenGate Licensing Pitfalls and Risks

Several licensing pitfalls frequently occur with Oracle GoldenGate deployments:

Incorrect Core Factor Application

Organizations commonly misunderstand or incorrectly apply Oracle’s Core Factor Table, leading to under-licensing or compliance violations.

Example Pitfall:

• A company mistakenly applies an incorrect core factor, counting AMD EPYC CPUs at 0.25 instead of the correct 0.5, resulting in under-licensing.

Virtualization and VMware Cluster Mistakes

Many organizations fail to license the entire physical VMware cluster when running GoldenGate on limited virtual CPUs, causing significant compliance exposure.

Example Pitfall:

• GoldenGate installed on one small VM within a large VMware cluster without licensing all physical cores, resulting in significant licensing gaps identified during Oracle audits.

Cloud Licensing Errors

Organizations often mistakenly apply Oracle’s on-premises core factor rules to cloud deployments, leading to inaccurate license counts and compliance violations.

Example Pitfall:

• An enterprise deploying GoldenGate on AWS mistakenly applies Oracle’s Core Factor Table (0.5) instead of using Oracle’s 2 vCPUs = 1 processor license rule, causing a severe under-licensing error.

Oracle GoldenGate Licensing Restrictions and Limitations

GoldenGate licenses carry certain explicit restrictions and limitations that organizations must observe:

No Named User Plus Licensing Option

• Oracle GoldenGate is typically licensed exclusively using Processor licenses.
• No Named User licensing is usually permitted for GoldenGate, limiting flexibility in user-based scenarios.

Disaster Recovery and Standby Licensing Rules

• Oracle typically requires licensing GoldenGate in primary and standby/DR environments if active replication occurs.
• GoldenGate instances for failover or standby systems are often required to be fully licensed unless explicitly negotiated otherwise.

Oracle GoldenGate Licensing Best Practices

Organizations can effectively manage Oracle GoldenGate licenses by consistently applying clear licensing best practices:

Maintain Accurate Licensing Documentation

• Clearly document GoldenGate licensing entitlements, core factor calculations, and centrally deployed hardware or cloud infrastructure details.

Regular Internal Licensing Audits

• Perform quarterly or annual internal compliance audits to proactively identify and correct GoldenGate licensing discrepancies.

Clear Understanding of Core Factors and Cloud Rules

• Regularly verify understanding of Oracle’s core factor table and cloud licensing rules, ensuring accurate licensing calculations.

Engage Licensing Experts for Complex Deployments

• To avoid costly mistakes, seek independent Oracle licensing expertise during virtualized, cloud-based, or large-scale GoldenGate deployments.

Oracle GoldenGate Licensing Audit Preparation

Oracle regularly audits GoldenGate deployments. Organizations must proactively prepare to reduce risks:

Maintain Audit-Ready Documentation

• Centralize GoldenGate licensing documentation clearly showing license entitlements, core factor calculations, hardware configurations, and virtual/cloud deployments.

Validate Licensing Regularly

• Conduct proactive internal GoldenGate licensing assessments regularly, documenting usage and licensing compliance.

Carefully Respond to Audit Requests

• Clearly respond to Oracle audit requests, promptly providing accurate, validated GoldenGate licensing data to minimize audit penalties or risks.

Practical Oracle GoldenGate Licensing Examples

Example Scenario 1: On-premises Processor Licensing Calculation

• Oracle GoldenGate deployed on-premises using Intel Xeon CPUs (20 cores total).
• Licensing required: 20 cores × 0.5 core factor = 10 Processor licenses.

Example Scenario 2: AWS GoldenGate Licensing

• AWS EC2 instance with 12 vCPUs running Oracle GoldenGate.
• Required Oracle licenses: 12 vCPUs ÷ 2 = 6 Processor licenses.

Example Scenario 3: VMware Cluster Licensing Pitfall

• VMware cluster with four physical hosts (64 cores total), Oracle GoldenGate running on one VM (only 8 vCPUs).
• Oracle requires licensing all 64 cores × 0.5 core factor = 32 processor licenses, despite limited VM usage.

Final Recommendations for Oracle GoldenGate License Management

Effective Oracle GoldenGate license management requires clearly defined processes, proactive compliance strategies, and accurate documentation practices:

• Document GoldenGate license entitlements, core calculations, deployments, and cloud usage details centrally.
• Regularly audit internal deployments proactively to identify and remediate licensing issues early.
• Communicate GoldenGate licensing rules and requirements internally, providing regular staff training.
• Seek independent licensing expertise periodically for complex environments or validation.

By consistently applying these comprehensive guidelines, organizations can effectively manage Oracle GoldenGate licenses, minimize compliance risks, optimize licensing spend, and maximize long-term value from their data replication and integration investments.

Do you want to know more about our Oracle License Management Services?

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit