Oracle GoldenGate Licensing in Cloud and Hybrid Environments
Executive Summary: Oracle GoldenGate deployments increasingly span on-premises data centers and public clouds.
This article provides CIOs, CTOs, and IT asset managers a clear guide to licensing GoldenGate in cloud and hybrid environments, including Amazon Web Services (AWS), Microsoft Azure, and Oracle Cloud Infrastructure (OCI).
We explain how Oracle’s cloud licensing policy works, how to ensure compliance when moving GoldenGate workloads to the cloud, and strategies to optimize costs across hybrid deployments.
GoldenGate on AWS and Azure (BYOL Licensing)
Oracle’s standard cloud policy applies to GoldenGate on AWS/Azure. In these clouds, Oracle counts two vCPUs as one Processor license (no on-prem core factor is used).
You must license all virtual CPUs allocated to any VM where GoldenGate runs. For example, an eight-vCPU instance in AWS requires four GoldenGate processor licenses.
This is a Bring Your Own License (BYOL) scenario. For cloud deployment, you can use existing licenses or purchase new ones.
There is no special “cloud-only” GoldenGate license; your on-prem entitlements can be used in the cloud if they’re not simultaneously used elsewhere (and you have active support).
Always remember to license both the source and target systems.
In a hybrid setup (say, replicating from an on-prem Oracle database to an Azure database using GoldenGate), the on-prem server needs GoldenGate licenses (count cores with Oracle’s factor, e.g., 0.5 per Intel core), and the Azure VM needs licenses based on its vCPUs (2 vCPUs = 1 license).
Each environment running GoldenGate must be licensed, even if one side is Oracle and the other is non-Oracle or cloud.
GoldenGate on Oracle Cloud (OCI) Service
In Oracle’s own cloud (OCI), GoldenGate is a managed cloud service billed by the OCPU hour (Oracle CPU hour).
In this model, the cloud subscription includes the GoldenGate software license cost, and you pay only for the compute time you use.
Oracle’s published rate is about ~$0.32 per OCPU-hour (check current pricing). So, deploying 4 OCPUs continuously for a month could incur a few hundred dollars in charges.
BYOL option: If you already own GoldenGate licenses, OCI allows a Bring Your Own License mode, in which you use your licenses and pay a lower rate for the service.
Using BYOL can save costs if you have long-running, steady workloads and spare on-prem licenses. In contrast, the license-included hourly model is convenient for short-term or variable workloads.
Read Oracle GoldenGate Licensing for Non-Oracle Databases and Big Data.
Hybrid Deployment Scenarios (On-Premises to Cloud)
For hybrid environments (on-premises to cloud) or multi-cloud replication, each environment running GoldenGate must be licensed according to its platform.
On-prem servers count physical cores (with Oracle’s core factor), and cloud instances count vCPUs (2 vCPUs = 1 license).
Even standby or disaster-recovery instances in the cloud require licensing if GoldenGate is installed and actively applying data – Oracle doesn’t provide free standby rights for GoldenGate.
Plan your architecture assuming every active GoldenGate process must be fully licensed, whether in a data center or any cloud.
Recommendations
- Apply Official Cloud Rules: Always use Oracle’s two vCPU = 1 license rule for AWS/Azure. Do not apply on-premises core factors in the public cloud—a common mistake that can cause compliance gaps.
- License Both Ends: In any hybrid or multi-cloud setup, remember that every GoldenGate environment requires licensing. There’s no free pass for target or source systems just because they’re in the cloud.
- Monitor Cloud Usage: If using OCI GoldenGate pay-as-you-go, closely monitor OCPU hours. Shut down GoldenGate instances when not actively needed (e.g. in dev/test) to save on hourly costs.
- Leverage BYOL: If you already paid for perpetual GoldenGate licenses and have active support, use those licenses in cloud deployments (including OCI’s BYOL option) to avoid paying twice.
- Compare Costs: Evaluate the total cost of running GoldenGate in the cloud vs on-prem. For steady 24/7 workloads, owning licenses might be cheaper over a 3-5 5-year period. For variable or short-term needs, cloud subscriptions can be more cost-effective.
- Document Deployments: Record all GoldenGate instances in the cloud, their vCPU counts, and which licenses cover them. Good documentation helps demonstrate compliance during audits and prevents accidental under-licensing after scaling up resources.
FAQ
Q1: How do I calculate GoldenGate licenses for an AWS VM?
A: Divide the number of vCPUs by 2 (Oracle’s policy). Always round up to the next whole license. For example, an eight vCPU AWS instance needs 4 GoldenGate processor licenses.
Q2: Does Oracle’s core factor apply in Azure/AWS?
A: No. Public clouds do not use the on-prem core factor (e.g., 0.5 per core). Oracle uses the simple rule that two vCPUs = one license in AWS and Azure, regardless of core type.
Q3: Can one GoldenGate license cover both on-prem and cloud servers?
A: No. Each environment requires its own licensed GoldenGate instance. In a hybrid setup, you will use one set of licenses for the on-prem server and another for the cloud server – you can’t “share” a license between them simultaneously.
Q4: What is GoldenGate BYOL in Oracle Cloud?
A: BYOL (“Bring Your Own License”) allows you to apply your existing GoldenGate licenses to the OCI GoldenGate service. In BYOL mode, you pay a lower hourly cloud rate because your existing entitlements cover the license cost.
Q5: If I stop an OCI GoldenGate instance, do charges stop?
A: Yes. Billing is based on OCPU hours consumed while the service is running. If you shut down or terminate the GoldenGate deployment in OCI, you cease incurring OCPU charges.
Q6: Do I need a license for GoldenGate on a DR (standby) cloud server?
A: Yes. Any system where GoldenGate is installed and active, even just applying changes for DR, requires a license or subscription. Oracle’s 10-day failover rule (which exists for databases in certain scenarios) does not exempt GoldenGate.
Q7: Are there any free or trial options for GoldenGate in the cloud?
A: Not really, aside from limited-time cloud trial credits. Oracle may provide OCI credits that could be used to run the GoldenGate Service temporarily, but there is no free GoldenGate edition for production use. It’s a fully licensed product.
Q8: Can I move GoldenGate licenses from on-prem to cloud and back?
A: Yes. Oracle allows redeploying your GoldenGate licenses between on-premises and cloud (assuming you’re compliant on the cloud with the 2-vCPU rule). Ensure you’re not running the same license in two places simultaneously. Keeping good records is important when shifting licenses.
Q9: How is GoldenGate licensed on Azure or AWS relative to Oracle’s core factor?
A: In AWS/Azure, ignore the core factor table. Use the cloud policy: count vCPUs and divide by 2. For example, 4 vCPUs = 2 licenses. Oracle’s core factor (0.5 for Intel) only matters for on-prem hardware.
Q10: What does GoldenGate cost?
A: As of current pricing, the list price is $17,500 per processor license (for any GoldenGate variant). Keep in mind that you’ll typically also pay annual support (~22% of the net license price). Many organizations negotiate discounts off the list price in enterprise deals.
