GoldenGate Licensing Fundamentals
Oracle GoldenGate is a real-time data replication and integration platform used for database migration, disaster recovery, zero-downtime upgrades, and streaming analytics. Its licensing model is Processor-based — you licence the physical cores (adjusted by Oracle's Core Factor Table) on every server where GoldenGate processes run.
The most critical licensing rule: you must licence both source and target. If GoldenGate captures changes from Server A and applies them to Server B, both servers require GoldenGate Processor licences. This dual-licensing requirement is the single most common source of under-licensing in GoldenGate deployments — organisations frequently forget to licence the target side, or assume the DR standby does not require licensing.
GoldenGate licensing does not depend on the number of replication streams, tables replicated, or data volume. Whether you replicate 5 tables or 5,000, the licence cost is determined solely by the Processor count of the servers involved. This makes GoldenGate cost-effective for large-scale replication — once you have licensed the servers, you can replicate as much data as the infrastructure supports without additional licence costs. However, it also means that even a tiny replication job on a large server carries the full Processor licensing burden for that server's entire core count.
🎯 Core Licensing Rules
- Processor metric only: GoldenGate is licensed exclusively per Processor. Named User Plus (NUP) is not available for production deployments in standard Oracle agreements.
- Source AND target: Every server running GoldenGate extract or apply processes must be licensed — no exceptions for DR, standby, or read-only targets.
- Core Factor applies on-premises: Intel/AMD x86 = 0.5, SPARC T-series = 0.25, IBM POWER = 1.0. A 16-core Intel server requires 8 Processor licences.
- No Core Factor in cloud: On AWS/Azure, 2 vCPUs = 1 Processor licence. On OCI, 1 OCPU = 1 Processor licence under BYOL.
- VMware full-cluster rule applies: If GoldenGate runs on any VM in a VMware cluster, all physical cores across all hosts must be licensed.
- Annual support at ~22%: Perpetual licences require annual support renewal — approximately $3,850/yr per Processor licence at list price.
GoldenGate Editions: Which Licence Do You Need?
| Edition | Use Case | List Price/Processor | What Must Be Licensed |
|---|---|---|---|
| GoldenGate for Oracle Database | Oracle-to-Oracle replication | $17,500 | Source Oracle DB server + Target Oracle DB server |
| GoldenGate for Non-Oracle Database | SQL Server, MySQL, PostgreSQL, Db2, etc. | $17,500 | Source non-Oracle DB server + Target non-Oracle DB server |
| GoldenGate for Big Data | Kafka, Hadoop, HBase, MongoDB, Cassandra | $20,000 | Source database servers only — target cluster is licence-free |
| GoldenGate for Mainframe | DB2 z/OS, legacy mainframe systems | ~$100,000 | Mainframe processors + other-side DB server |
| GoldenGate Veridata | Data comparison and validation | ~$30,000 | Servers running Veridata processes |
"Cross-platform replication requires two licence types. Replicating from Oracle Database to SQL Server requires GoldenGate for Oracle Database on the source AND GoldenGate for Non-Oracle Database on the target — effectively doubling your licence cost for that pipeline."
Licensing for Oracle-to-Oracle Replication
The most common deployment: replicating between two Oracle databases for disaster recovery, reporting offload, or zero-downtime migration. Both the source and target Oracle DB servers must be fully licensed with GoldenGate for Oracle Database.
Oracle-to-Oracle DR Replication
Setup: Production Oracle DB on a 2-socket Intel Xeon server (16 cores per socket = 32 cores total). DR Oracle DB on an identical server. GoldenGate captures changes from production and applies them to DR.
Licence calculation: Each server: 32 cores × 0.5 Core Factor = 16 Processor licences. Two servers = 32 Processor licences total.
Takeaway: Always include DR and standby servers in your GoldenGate licence count. The source-and-target rule has no exception for passive or read-only targets.
A key benefit of the Oracle Database edition: it includes a restricted-use licence for Oracle Active Data Guard and XStream on the same databases. You do not need to purchase Active Data Guard separately if you already hold GoldenGate licences for those servers.
A key benefit of the Oracle Database edition: it includes a restricted-use licence for Oracle Active Data Guard and XStream on the same databases. You do not need to purchase Active Data Guard separately if you already hold GoldenGate licences for those servers.
High Availability and Disaster Recovery Licensing
GoldenGate is frequently deployed for high availability (active-active replication) and disaster recovery (active-passive standby). Both scenarios require full licensing on every server running GoldenGate processes — there is no automatic "standby exemption" for GoldenGate.
Active-Active Replication
Both database servers capture and apply changes simultaneously. Both require GoldenGate Processor licences for the full core count. There is no reduced-rate licence for bi-directional replication — each server is both a source and a target, and must be fully licensed.
Active-Passive DR
GoldenGate runs on both the production (active) server and the DR (passive) server. Even though the DR server only applies changes and does not serve application traffic, it runs GoldenGate apply processes and must be licensed. Oracle does not offer a reduced DR rate for GoldenGate — unlike Oracle Database, which has a limited 10-day failover allowance, GoldenGate has no equivalent exemption. The DR server requires the same number of Processor licences as the production server.
Negotiated DR Terms
Some organisations have negotiated specific DR terms into their Oracle contracts — for example, reduced licensing for servers that are only activated during failover events. These are non-standard terms that require explicit contract language. Do not assume Oracle's standard policies include any DR concession for GoldenGate. If DR licensing cost is a concern, negotiate specific terms before signing or renewing your Oracle agreement.
Licensing for Non-Oracle and Cross-Platform Replication
When replicating between Oracle and non-Oracle databases (or between two non-Oracle databases), you need the appropriate GoldenGate edition for each side of the pipeline. The licence types do not cross-cover — a GoldenGate for Oracle Database licence does not cover a SQL Server target.
| Replication Scenario | Source Licence | Target Licence | Example Cost (8-core servers, 0.5 CF) |
|---|---|---|---|
| Oracle → Oracle | GG for Oracle (4 Proc) | GG for Oracle (4 Proc) | 8 × $17,500 = $140,000 |
| Oracle → SQL Server | GG for Oracle (4 Proc) | GG for Non-Oracle (4 Proc) | 4 × $17,500 + 4 × $17,500 = $140,000 |
| SQL Server → PostgreSQL | GG for Non-Oracle (4 Proc) | GG for Non-Oracle (4 Proc) | 8 × $17,500 = $140,000 |
| Oracle → Kafka (Big Data) | GG for Big Data (4 Proc) | None (target licence-free) | 4 × $20,000 = $80,000 |
| Oracle → Kafka → SQL Server | GG for Big Data (Oracle source) + GG for Non-Oracle (SQL Server target) | Both sides licensed | 4 × $20,000 + 4 × $17,500 = $150,000 |
Need Expert Oracle Licensing Guidance?
Redress Compliance provides independent Oracle licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic license optimization, audit defense, and contract negotiation.
Explore Oracle Advisory Services →GoldenGate for Big Data: The One-Sided Licensing Advantage
GoldenGate for Big Data is the most cost-efficient edition for streaming data into analytics platforms because Oracle only requires licensing on the source side. The target cluster — whether Hadoop, Kafka, HBase, MongoDB, or Cassandra — does not require GoldenGate licences regardless of how many nodes it contains.
🎯 Big Data Licensing Rules
- Source databases only: Licence the Processor count of each source database server feeding data into the Big Data pipeline. The target cluster is licence-free.
- Messaging systems (Kafka/JMS): If the source is a messaging system rather than a database, every 25 message queues or topics counts as 1 Processor licence. A Kafka cluster with 100 topics requires 4 Processor licences.
- Multiple sources: Sum all source server Processors across all databases and messaging systems feeding the pipeline.
- Higher per-Processor price: $20,000/Processor vs $17,500 for standard editions — but licensing only one side typically makes Big Data the cheaper option for analytics pipelines.
📊 Free Assessment Tool
Planning a GoldenGate deployment? Our free database licensing calculator helps you count processor licences across source and target, apply core factors, and estimate total cost.
Take the Free Assessment →Cloud Deployment: OCI, AWS, and Azure
Pay-as-You-Go — No Perpetual Licence Needed
Oracle's managed GoldenGate service on OCI. Billed by OCPU per hour (~$0.32/OCPU-hour). No upfront licence cost — the subscription includes the software licence, infrastructure, patching, and monitoring. Ideal for variable workloads where you can scale OCPUs up/down. 8 OCPUs running 24×7 ≈ $15,000/month (~$180K/year). BYOL option available if you hold existing perpetual licences.
Bring Your Own Licence + Cloud Infrastructure
Deploy GoldenGate on EC2/Azure VMs using your perpetual licences. No Core Factor in the cloud: 2 vCPUs = 1 Processor licence. A 16-vCPU instance requires 8 Processor licences. Both source and target cloud VMs must be licensed. Active Oracle Support is required for BYOL eligibility. Right-size instances carefully — every unnecessary vCPU pair adds one Processor licence ($17,500 at list). Performance-tune GoldenGate before scaling up cloud instances to avoid paying for unnecessary licensing overhead that delivers no replication benefit.
Financial Services: VMware Cluster Audit — $1.12M Exposure
Situation: A US financial services company deployed GoldenGate on a single VM within an 8-node VMware cluster with vMotion enabled. The VM used 8 vCPUs. The internal team calculated 4 Processor licences (8 vCPUs × 0.5).
Audit finding: Oracle applied soft partitioning rules: 8 nodes × 2 sockets × 16 cores = 256 physical cores × 0.5 = 128 Processor licences required. 128 × $17,500 = $2.24M at list price — for both source and target GoldenGate processes running in the cluster.
Takeaway: GoldenGate is subject to the same VMware full-cluster licensing rule as Oracle Database. A single GoldenGate VM on a shared cluster can generate seven-figure audit findings. Always isolate GoldenGate on dedicated hosts or use Oracle-approved hard partitioning.
Virtualisation: The Most Expensive GoldenGate Licensing Trap
Oracle's soft partitioning rules apply to GoldenGate identically to Oracle Database. If GoldenGate runs on any VM within a VMware, Hyper-V, or KVM cluster with live migration enabled, Oracle requires licensing all physical cores across all hosts in the cluster — not just the VM's allocated resources.
This is particularly devastating for GoldenGate because it is an infrastructure tool that IT teams routinely deploy on shared virtual infrastructure without involving the licensing team. A single GoldenGate VM on a 10-node VMware cluster can require licensing 200+ physical cores — costing $1.75M+ at list price for a tool that is using 4 vCPUs of actual capacity.
The only Oracle-approved hard partitioning technology for x86 environments is Oracle VM with pinned vCPUs. Solaris Zones (capped) and IBM LPAR (capped) are approved for their respective platforms. All other virtualisation technologies — VMware, Hyper-V, KVM, Nutanix AHV, Proxmox — are classified as soft partitioning and trigger full-cluster licensing.
Common Compliance Pitfalls
| Pitfall | What Happens | Typical Financial Impact |
|---|---|---|
| Forgetting to licence the target | Only source server is licensed; target DR/reporting server has no GoldenGate licences | Full list price for all target server cores — $100K–$500K+ |
| VMware full-cluster exposure | GoldenGate on shared VMware cluster — Oracle demands licensing all hosts | 4–10× expected cost — $500K–$2M+ |
| Wrong edition for cross-platform | Using GoldenGate for Oracle licence on SQL Server target | Requires separate Non-Oracle edition — doubling licence requirement |
| Applying Core Factor in cloud | Calculating AWS licences with 0.5 Core Factor instead of 2 vCPU = 1 rule | 50% under-licensed in cloud deployments |
| Unlicensed development/test instances | GoldenGate running in dev/test environments without licences | Full Processor licensing required unless GoldenGate Free is used |
| Big Data edition on database targets | Using GoldenGate for Big Data to replicate to a relational database | Wrong edition — requires Oracle or Non-Oracle edition for DB targets |
Cost Optimisation Strategies
Isolate GoldenGate on Dedicated Hosts
The single most impactful cost reduction. Move GoldenGate off shared VMware clusters onto dedicated hosts (or Oracle VM with pinned vCPUs). This eliminates the full-cluster licensing trap and can reduce your Processor count by 60–90%.
Use GoldenGate Free for Non-Production
Oracle GoldenGate Free provides full replication functionality at no cost for development, testing, and sandbox environments. Deploy GoldenGate Free in Docker containers for all non-production use and reserve paid licences exclusively for production servers.
Right-Size Server Hardware
Every additional core on a GoldenGate server adds 0.5 Processor licences at $17,500 each. If GoldenGate runs on a 32-core server but would perform identically on 16 cores, downsizing saves 8 Processor licences ($140,000 at list). Performance-tune before scaling up.
Leverage Big Data Edition for Analytics Pipelines
If your target is Kafka, Hadoop, or a NoSQL platform, use GoldenGate for Big Data — licensing only the source side. This can halve your licence cost compared to using the standard edition with source-and-target licensing.
Evaluate OCI GoldenGate for Variable Workloads
For migration projects or intermittent replication, OCI GoldenGate's pay-per-hour model avoids perpetual licence investment. A 3-month migration at 8 OCPUs costs ~$45K in OCI fees versus $280K+ in perpetual licences for the equivalent on-premises deployment. After migration, shut down the service and stop paying.
Related Reading
Related Guides
Explore More Licensing Hubs
Ready to Take Control of Your Software Licensing?
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →