GoldenGate for non Oracle and Big Data: both ends count.

Oracle GoldenGate for non Oracle databases and Big Data is licensed per processor on both ends of the replication path, so the cost question is the core count on every source and target, not just the Oracle system.

This guide is for data, integration, and procurement leaders running GoldenGate across mixed platforms in 2026. Pair it with the GoldenGate licensing guide and the Oracle Practice so the architecture and the entitlements match.

How is GoldenGate licensed across platforms?

GoldenGate licenses per processor core on the systems running its processes. There is an edition for Oracle databases, a distinct edition for non Oracle databases, and a separate product for Big Data targets.

Oracle describes the product family on its Oracle GoldenGate page. The licensing detail to confirm is which edition applies to each platform you run.

Which edition covers which platform?

The Oracle edition covers Oracle Database sources and targets. The non Oracle edition covers databases such as SQL Server, MySQL, and PostgreSQL. GoldenGate for Big Data covers streaming and analytics targets.

• Oracle edition: for Oracle Database source and target systems.
• Non Oracle edition: for SQL Server, MySQL, PostgreSQL and similar.
• Big Data: for Kafka, Hadoop, and cloud object store targets.

How does GoldenGate for Big Data differ?

GoldenGate for Big Data delivers change data into streaming and analytics platforms rather than into a relational target. It licenses per processor on the delivery systems, so the Big Data side carries its own core count.

Where do you count cores for GoldenGate?

You count where GoldenGate runs its capture and delivery processes. That is usually both the source and the target. The target side is the part most estates forget when they budget.

Why are target side cores so often missed?

Budgets tend to start from the Oracle source and stop there. The target database or Big Data platform runs a delivery process that also needs licensing, and that omission surfaces in an audit.

What makes heterogeneous estates harder to count?

A path that crosses Oracle, a non Oracle database, and a Big Data target uses three different licensing treatments at once. Counting the whole path correctly means tracking each platform's edition and cores separately.

How do you cut GoldenGate cost safely?

Consolidate capture and delivery onto fewer well sized cores, confirm the right edition per platform, and retire replication paths no longer in use. The core count on both ends is the lever.

What replication paths can usually be retired?

Paths built for a migration that has finished, or for a report feed now served another way, often keep running and keep consuming licenses. Retiring them removes cost with no operational loss.

What to do next

1. Map every GoldenGate capture and delivery process across platforms.
2. Identify the correct edition for each source and target.
3. Count processor cores on both the source and the target sides.
4. Flag any Big Data target running its own delivery process.
5. Retire replication paths left over from finished projects.
6. Consolidate processes onto fewer, well sized cores.
7. Reconcile the counted cores to entitlements before renewal.

Frequently asked questions

How is Oracle GoldenGate licensed for non Oracle databases in 2026?

GoldenGate licenses per processor core on the database it runs against, and a separate edition covers non Oracle databases. The metric to confirm is the core count on the source and target systems, because GoldenGate is licensed where it captures and where it delivers, not once.

Does GoldenGate for non Oracle cost the same as for Oracle?

No. Oracle sells a distinct GoldenGate edition for non Oracle databases, and the rate and terms differ from the Oracle Database edition. Assuming one price across both is a common budgeting error, so price the non Oracle edition on its own terms.

How does GoldenGate for Big Data license?

GoldenGate for Big Data is a separate product that delivers change data into targets such as Kafka, Hadoop, and cloud object stores. It licenses per processor on the systems running the delivery process, so the Big Data targets, not just the source, drive the count.

Do you license GoldenGate on both source and target?

Generally yes. GoldenGate captures changes on the source and applies them on the target, and both sides run licensable processes. The frequent surprise in an audit is target side cores that were never counted at purchase.

Can you reduce GoldenGate licensing cost?

Yes, by consolidating capture and delivery onto fewer, well sized cores, by confirming the correct edition for each platform, and by retiring replication paths no longer in use. The core count on both ends is the lever, so shrinking it shrinks the bill.

What is the biggest GoldenGate licensing risk in an audit?

The biggest risk is uncounted target side cores and the wrong edition applied to a non Oracle or Big Data platform. Because GoldenGate spans heterogeneous systems, the estate is easy to under count when only the Oracle source is in view.