Oracle GoldenGate Licensing for Non-Oracle Databases and Big Data

Oracle GoldenGate Licensing for Non-Oracle Databases and Big Data

Executive Summary: Oracle GoldenGate isn’t just for Oracle-to-Oracle database replication – it’s widely used to integrate heterogeneous systems.

This article explains how to license GoldenGate in non-Oracle database environments and for big data targets.

Enterprise architects and license managers will learn about the additional GoldenGate modules (SQL Server, DB2, MySQL, Hadoop, Kafka, etc.), their costs, and how to ensure compliance when replicating across diverse platforms.

GoldenGate Editions and Add-On Modules

Oracle offers different GoldenGate license types depending on the source and target systems:

• Oracle GoldenGate (Base) – The standard edition for Oracle-to-Oracle database replication. Licensed per processor (list price around $17,500 per processor). This applies when both the source and target are Oracle databases.
• GoldenGate for Non-Oracle Database – Required when GoldenGate connects Oracle databases with other database platforms, or for replication solely between non-Oracle databases. Priced roughly the same as the base license (~$17,500 per processor). This extends GoldenGate’s functionality to systems such as SQL Server, DB2, and MySQL, among others.
• GoldenGate for Big Data – A module for streaming data into big data systems and messaging platforms (e.g., Hadoop HDFS, Kafka, NoSQL stores). The list price (around $20,000 per processor) is higher since it’s specialized. It allows GoldenGate to deliver captured data to big data targets via various adapters.
• GoldenGate for Mainframe – A specialized (and very expensive) version to replicate with mainframe databases (like IBM DB2 on z/OS, VSAM, IMS). This license costs approximately $100,000 per processor due to the mainframe’s complexity. It’s only needed if the source or target system is a mainframe environment.

Each of these licenses is additive. Suppose your GoldenGate configuration involves an Oracle database on one side and a SQL Server on the other.

In that case, you need the base GoldenGate license (for the Oracle side) and the GoldenGate for Non-Oracle Database license (for the SQL Server side).

The same concept applies to big data and mainframes: you must have the specific module licensed for every environment in which GoldenGate interacts.

Owning a base GoldenGate license does not entitle you to use the non-Oracle or big data modules – each is a separate product.

Read this Oracle GoldenGate Licensing Negotiation Strategies for CIOs and CTOs

Licensing Scenarios and Examples

To clarify how these licenses work in practice, here are common replication scenarios and their requirements:

Licenses are needed for every server where GoldenGate capture or apply processes run.

For example, replicating data from an Oracle database to a Hadoop cluster involves GoldenGate on the Oracle server (which requires a base license) and GoldenGate on a Hadoop node (which requires a Big Data module license).

Using GoldenGate for a non-Oracle platform without the proper module license is a compliance violation and will be flagged in an audit.

Cost and Compliance Considerations

Licensing GoldenGate in heterogeneous environments can become expensive, so cost planning is vital. Pricing: Base GoldenGate and GoldenGate for Non-Oracle Database are about $17,500 per processor.

Big Data integration costs approximately $20,000 per processor, while mainframe integration is the most expensive, at roughly $ 100,000 per processor. Oracle also charges annual support fees (~22% of the license price) on each product.

To remain compliant, ensure the appropriate license type covers every environment where GoldenGate runs. This includes production, disaster recovery, test, and development systems – no free or discounted GoldenGate licenses are specifically for non-production use.

Oracle’s auditors often find compliance issues when a company uses GoldenGate for a non-Oracle target (say, SQL Server or MongoDB) without purchasing the corresponding module.

Avoid this by proactively licensing all needed components; it’s far cheaper than paying for licenses (plus back support) during an audit.

Recommendations

• Map Your Data Flows: Inventory every source and target in your GoldenGate configuration. Determine which GoldenGate module applies to each endpoint (Oracle, non-Oracle, big data, mainframe) so you can acquire the correct licenses.
• License Both Sides: Always license every participating environment. If data is moved between an Oracle database and a SQL Server, budget for two licenses (one base and one non-Oracle module). If it’s Oracle to Kafka, budget for the base + Big Data module, and so on.
• Budget for Mainframe: If your project involves mainframe data replication, note the extremely high cost of GoldenGate for Mainframe. Plan for it early or consider alternative approaches for those systems if possible.
• Track Entitlements: Maintain clear records of which GoldenGate licenses (and for which modules) you own. In complex environments, maintain documentation to prevent inadvertently deploying GoldenGate in new ways without proper licensing.
• Include Non-Production: Don’t overlook dev, test, or QA environments. If GoldenGate is used there, those systems need to be licensed. To minimize cost, you might restrict GoldenGate to only run on licensed production servers for testing or use short-term licenses.
• Consider Term Licenses: For short-term integration needs (such as a one-time migration project between Oracle and SQL Server), consider Oracle’s 1-year term licenses for GoldenGate modules instead of purchasing perpetual licenses. Term licenses cost a fraction of full price and can economically cover temporary use cases.

FAQ

Q1: If I have Oracle GoldenGate licenses, can I use them for non-Oracle databases?
A: Not by themselves. A standard GoldenGate (Oracle) license covers only Oracle-to-Oracle replication. To work with a non-Oracle database, you need the GoldenGate for Non-Oracle Database license for that system (in addition to any Oracle-side license).

Q2: Do I need to license GoldenGate on source and target when one is Oracle and one is SQL Server?
A: Yes. Each server running GoldenGate components needs its license. So in an Oracle-to-SQL Server scenario, the Oracle database server needs a GoldenGate (base) license, and the SQL Server needs a GoldenGate for Non-Oracle Database license.

Q3: Our source is Oracle, and the target is Kafka. What licenses are required?
A: You would need an Oracle GoldenGate license for the Oracle source, and a GoldenGate for Big Data license for the Kafka (big data) target platform.

Q4: If we replicate data between two SQL Servers (no Oracle DB involved), do we need the base Oracle GoldenGate license?
A: No. In that case, you would purchase GoldenGate for non-Oracle database licenses for each SQL Server node. The base Oracle GoldenGate license is only required when an Oracle database is part of the replication configuration.

Q5: Does GoldenGate for Mainframe cost $100k per processor?
A: Approximately yes (list price). It’s an order of magnitude more expensive than other GoldenGate licenses. This reflects the niche, complex nature of mainframe integration. Always verify current pricing, but expect a very high cost.

Q6: Is Named User Plus licensing available for GoldenGate?
A: Oracle does list a Named User Plus option (with a 25-user minimum per processor) for GoldenGate products, but it’s rarely used. GoldenGate is typically licensed per processor because it’s an infrastructure-level tool. NUP licensing may only be applicable in very small or specialized deployments.

Q7: Do we need GoldenGate licenses for development or test servers?
A: Yes, if GoldenGate is installed and running on those servers. Oracle requires licensing for any environment (production or non-production) where the software is used. Some firms limit GoldenGate to production systems and use workarounds for testing to avoid extra licenses, but if you do use it in dev/test, include those in your license count.

Q8: What happens if we use GoldenGate for a database without the proper module license?
A: You would be out of compliance. For example, using GoldenGate to replicate from Oracle to MySQL without a GoldenGate for Non-Oracle license for the MySQL side violates Oracle’s terms. In an audit, Oracle would likely demand you purchase the missing licenses (and support for the lapsed period). It’s best to license correctly upfront to avoid this scenario.

Q9: Can GoldenGate for Big Data output to multiple target systems with one license?
A: Yes. The GoldenGate for Big Data license covers the use of its adapters on a server, and those adapters can feed multiple target technologies (Kafka, HDFS, Cassandra, etc.) from that one licensed server. You don’t need separate licenses for each type of big data target – just license the server running the GoldenGate Big Data processes.

Q10: Is there an Oracle GoldenGate bundle that includes all these modules?
A: Not as a standard SKU. Oracle sells each GoldenGate module separately. However, during negotiations for a large purchase, you may seek a custom agreement or an enterprise license that encompasses multiple GoldenGate modules under one deal. That would be a special arrangement, not an off-the-shelf bundle.

Read more about our Oracle License Management Services.

Do you want to know more about our Oracle Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit