GoldenGate Pricing by Edition
Oracle GoldenGate licensing is per processor, and the rate depends on what you are replicating. Base GoldenGate — Oracle-to-Oracle — lists at $17,500 per processor. GoldenGate for Non-Oracle Database is also around $17,500 per processor; GoldenGate for Big Data is around $20,000 per processor; and GoldenGate for Mainframe sits at roughly $100,000 per processor, reflecting the specialised, low-competition nature of mainframe integration. On top of every licence sits annual support at 22% of net — about $3,850 per processor per year on the base edition — escalating roughly 8% each year under Oracle's standard terms.
Those rates look manageable per processor, but GoldenGate cost is driven by processor count and edition mix, not the headline rate. A modest replication topology spanning several multi-core hosts scales quickly, and the same per-processor discipline that governs the wider advanced Oracle licensing estate applies here: count every processor that touches the data flow before you model the cost.
| Edition | List (per processor) | Annual support (~22%) |
|---|---|---|
| GoldenGate (Oracle-to-Oracle) | $17,500 | ~$3,850 |
| GoldenGate for Non-Oracle Database | ~$17,500 | ~$3,850 |
| GoldenGate for Big Data | ~$20,000 | ~$4,400 |
| GoldenGate for Mainframe | ~$100,000 | ~$22,000 |
The Source-and-Target Rule
The defining feature of GoldenGate licensing is that it applies on both ends of the replication. You must license every server where GoldenGate captures, pumps or delivers data — the source where the Extract process runs, and the target where Replicat applies the changes. This dual-side rule is the single most common source of underestimation in GoldenGate cost models, because teams budget for the source database and quietly forget that the target carries an identical per-processor charge.
A bidirectional GoldenGate deployment across two 8-processor hosts is not 8 processors of licence — it is 16. Budgeting for one side effectively halves the figure you present to finance, and the gap surfaces at the worst possible moment: an Oracle audit.
This is precisely the kind of exposure that drives the triggers in our audit frequency analysis, and it is why GoldenGate deployments should be inventoried as complete topologies, not individual servers. The same care that prevents stranded entitlements in a cloud migration prevents an under-licensed target here.
The Big Data Exception
There is one important relief in the rules. GoldenGate for Big Data is the exception to the symmetric source-and-target requirement: Oracle's policy requires licensing only on the source database side, and the big data target cluster nodes do not require GoldenGate for Big Data licences. For an enterprise streaming change data into a large Hadoop, Kafka or cloud-analytics target, that asymmetry is a genuine saving — a sprawling target cluster that would be ruinous to license processor-by-processor simply does not need GoldenGate licences at all.
The catch is that the relief only exists if you have actually bought the Big Data edition. Running Big Data adapters under a base GoldenGate licence is a compliance failure, not a clever optimisation. The edition you license must match the workload you run — the same metric-matching discipline that governs OCI pricing and Exadata licensing decisions across the estate.
The Three Audit Failures
Oracle's audits of GoldenGate deployments repeatedly surface the same three failures. First, replicating to or from a non-Oracle database without the GoldenGate for Non-Oracle Database edition — a common gap when a team adds a PostgreSQL or SQL Server endpoint to an existing Oracle-to-Oracle flow. Second, using GoldenGate for Big Data adapters under a base licence rather than the Big Data edition. Third, failing to license GoldenGate on the target system processors — the direct consequence of forgetting the source-and-target rule.
Each is treated as a compliance gap requiring back-dated licences and support, and the support back-charge interacts painfully with the reinstatement and matched-set rules. Proactively licensing every component is far cheaper than settling under audit, where Oracle holds the leverage.
Buying GoldenGate Well
GoldenGate is rarely bought in isolation, and that is the buyer's advantage. When it is part of a larger Database or cloud purchase, negotiate it as a package — Oracle's account teams will trade GoldenGate discount for commitment elsewhere. If you anticipate needing multiple editions over time, negotiate them together upfront rather than returning to list price each time a new endpoint appears. And if an audit has already found a gap, the settlement is negotiable: Oracle is often open to cloud credits or a moderate, forward-looking licence expansion rather than the full theoretical compliance figure — but only with someone at the table who knows where that flexibility sits. The Oracle vendor intelligence hub anchors this approach across the portfolio.
For the full GoldenGate cost model — the topology inventory template, the edition-matching matrix and the audit-settlement playbook — download the Oracle Negotiation Playbook, or request a confidential briefing before you size or settle a GoldenGate deployment.