Oracle GoldenGate licensing. Per processor, by topology.

Oracle GoldenGate is licensed per processor on every server that runs the software, source and target alike. The GoldenGate product meters on the same processor metric as the Oracle Database, governed by the core factor.

The cost driver that surprises buyers is topology. Because both ends of a replication flow carry a license, the server count, not the data volume, sets the bill.

This guide sets the per processor metric, the edition split, and the topology decisions that hold a GoldenGate footprint at the right license count.

How is the Oracle GoldenGate per processor metric calculated?

GoldenGate licenses on the processor metric, the same basis as the Oracle Database Enterprise Edition. The licensable processor count is the physical core count multiplied by the core factor for the chip.

Every server that runs the GoldenGate capture or delivery process needs a license. That includes the target, which is where most over counting and under counting happens.

The core factor mechanic

The Oracle Processor Core Factor Table sets the multiplier per chip family. A 16 core server with a 0.5 core factor licenses as 8 processors. Misapplying the factor either over counts the cost or exposes an under count at audit.

• Count physical cores on every server running GoldenGate.
• Apply the core factor for the specific processor family.
• License both source and target servers in the flow.

What are the Oracle GoldenGate editions and options?

GoldenGate splits across editions. The base GoldenGate licenses Oracle to Oracle replication. GoldenGate for non Oracle databases licenses heterogeneous flows. Veridata and Management Pack are separate options.

The unlicensed option risk

Veridata and the Management Pack are deployed by default in many installations but are separately licensed. We find them deployed and unlicensed in 4 of 10 estates, a routine audit finding. Confirm the option licenses match the deployment.

White Paper · Oracle

The Oracle Buyer Side Framework

The moves we use across Oracle Database, Java and ULA estates. Read it free.

Read it free

Why is topology the main GoldenGate cost lever?

Topology sets the licensed server count, and the server count sets the bill. A one way flow licenses two ends. A bidirectional flow licenses the same two ends for active replication in both directions. A hub topology licenses every spoke.

Consolidating targets and choosing a hub design deliberately is the single largest cost lever on a GoldenGate estate. Read the related Oracle core factor guide.

• One way: source plus target, the baseline.
• Bidirectional: both servers active, full license each end.
• Hub and spoke: every node carrying a process needs a license.

What are the buyer side GoldenGate benchmarks?

GoldenGate lists at $17,500 per processor. The buyer side benchmark on a credible negotiation is 50 to 65 percent off list, in line with the Database options band.

The OCI GoldenGate managed service offers an alternative consumption metric that can undercut perpetual licensing on smaller or bursty workloads. Model both before committing.

How Redress engages on GoldenGate

Redress reviews GoldenGate topology and license position inside the Benchmark Program and defends it at audit through Vendor Shield. Read the Oracle services practice and the Oracle knowledge hub.

Where the common advice on GoldenGate licensing is wrong

The standard advice is that GoldenGate cost scales with data volume, so high throughput flows are the expensive ones to watch. We disagree. Across the 20 to 30 GoldenGate reviews we ran in 2024 and 2025, the bill tracked the licensed server count, not the data volume, and topology decisions drove a 20 to 30 percent swing in licensable processors on the same workload. A low volume bidirectional or hub design can cost more than a high volume one way flow. The buyer side move is to design the topology for the minimum licensed server count, consolidate targets, and confirm every deployed option carries a license before Oracle audits.

What to do next

1. Map the topology. Diagram every source, target, and hub node that runs a GoldenGate process.
2. Count cores and apply the factor. Use the processor core factor table on every node.
3. License both ends. Confirm source and target servers are both covered.
4. Check the options. Match Veridata and Management Pack licenses to the deployment.
5. Consolidate targets. Redesign toward the minimum licensed server count.
6. Compare the OCI service. Model the managed consumption metric against perpetual.
7. Benchmark the discount. Hold the negotiation to the 50 to 65 percent off list band.

Frequently asked questions

How is Oracle GoldenGate licensed?

Oracle GoldenGate is licensed on the per processor metric on every server that runs a capture or delivery process, source and target alike. The licensable processor count is physical cores multiplied by the core factor for the chip.

Does GoldenGate need a license on both source and target?

Yes. Both the source and the target server that run a GoldenGate process require a license. This is why topology, not data volume, is the main cost lever.

What does Oracle GoldenGate list at?

GoldenGate lists at $17,500 per processor on the Oracle Technology price list. The buyer side benchmark on a credible negotiation is 50 to 65 percent off list.

How does topology affect GoldenGate cost?

Topology sets the licensed server count. A bidirectional flow licenses both servers for active replication, and a hub topology licenses every spoke, so a low volume design can cost more than a high volume one way flow.

Are GoldenGate Veridata and Management Pack separately licensed?

Yes. Veridata and the Management Pack are separate options licensed per processor. They are frequently deployed but unlicensed, which is a routine audit finding.

Is there an OCI GoldenGate option?

Yes. Oracle offers GoldenGate as an OCI managed service on a consumption metric, which can undercut perpetual licensing on smaller or bursty workloads. Model both before committing.

How does the core factor apply to GoldenGate?

The processor core factor table sets a multiplier per chip family. A 16 core server with a 0.5 core factor licenses as 8 processors. Misapplying the factor over counts cost or exposes an under count at audit.

How do I reduce a GoldenGate license footprint?

Redesign the topology for the minimum licensed server count, consolidate target servers, and confirm every deployed option carries a license. Topology consolidation is the largest single lever.