GoldenGate Licensing Overview

Introduction to Oracle GoldenGate Licensing

• Oracle GoldenGate Licensing: Oracle GoldenGate is a powerful tool for capturing real-time change data and moving large volumes of transactional data between databases. It requires licensing for both the source and target databases.
• Licensing Metrics: Oracle GoldenGate can be licensed with named user plus or processor metrics. The license fee for a processor is $17,500.
• Oracle Active Data Guard: Oracle Active Data Guard is included in Oracle GoldenGate licenses and does not need to be licensed separately.
• Common Compliance Issues: Common compliance issues include using GoldenGate for non-Oracle databases, not licensing source and target databases, and miscalculating the core factor table.

Overview of Oracle GoldenGate

How Exactly is Oracle GoldenGate Licensed?

Licensing Models:
Oracle GoldenGate offers two primary licensing models: Processor-Based Licensing and Named User Plus (NUP) Licensing.

Each model is tailored to different deployment scenarios and organizational needs.

• Processor-Based Licensing:
  This model requires you to license based on the number of processors where Oracle GoldenGate is installed and running. The number of processors is calculated using Oracle’s core factor table, which assigns a multiplier to the number of physical cores depending on the processor type. This model is ideal for environments where the number of users is not easily countable or where the workload is distributed across multiple processors
  .Example:
  If you have an 8-core server running Oracle GoldenGate and your processor’s core factor is 0.5, you must license 4 procesors (8 cores * 0.5 = 4 licenses).
• Named User Plus (NUP) Licensing:
  NUP licensing is based on the number of individuals or devices accessing the Oracle GoldenGate software. Minimum user requirements per processor must be met. This model is often used in non-production environments where the number of users is small and easily countable.
  Example:
  If you are using Oracle GoldenGate in a test environment with 50 users and the minimum requirement is 25 NUP licenses per processor, and you have 2 processors, you would need to purchase at least 50 NUP licenses (2 processors * 25 minimum NUP per processor).

Cloud and Hybrid Environments:
Oracle GoldenGate can be deployed in cloud, on-premises, or hybrid environments. When deployed in the cloud, the Bring Your Own License (BYOL) model allows you to apply your existing licenses to cloud instances, whether on Oracle Cloud Infrastructure (OCI), AWS, or Azure.

The same licensing rules for processor and NUP models apply in the cloud. Still, it’s essential to consider the specific cloud provider’s instance types and how they map to Oracle’s licensing requirements.

• BYOL Example:
  If you have an existing Oracle GoldenGate processor license, you can deploy it on a cloud VM with equivalent processing power. However, ensure the cloud instance’s virtual CPUs (vCPUs) match the licensed processors based on Oracle’s core factor table.

Oracle GoldenGate Components

List of Components:

• Oracle GoldenGate Core:
  The foundational component is responsible for data capture, transformation, and delivery across various platforms. It supports real-time data integration and replication.
• Oracle GoldenGate Management Pack:
  This component provides tools for managing, monitoring, and optimizing Oracle GoldenGate environments. It includes features like automated configuration management and comprehensive performance monitoring.
• Oracle GoldenGate Veridata:
  Veridata is used for data comparison and verification, ensuring that data replicated across systems is accurate and consistent. It helps identify and resolve data discrepancies between source and target systems.
• Oracle GoldenGate Studio:
  A design and deployment tool that simplifies the configuration and management of Oracle GoldenGate environments. It offers a graphical interface for designing data replication and integration processes.
• Oracle GoldenGate Monitor:
  This component provides real-time monitoring of Oracle GoldenGate processes, offering dashboards and alerts to ensure high availability and performance.
• Oracle GoldenGate for Big Data:
  Extends Oracle GoldenGate’s capabilities to big data platforms like Hadoop, Kafka, and NoSQL databases, enabling real-time data integration into big data ecosystems.

Functionality of Each Component:

Oracle GoldenGate for Big Data:
It enables integration with big data platforms, allowing organizations to leverage GoldenGate’s real-time data processing capabilities in modern data architectures. This is particularly useful for businesses that rely on big data analytics and must keep their data ecosystems synchronized.

Oracle GoldenGate Core:
Acts as the engine of the GoldenGate suite, handling the essential tasks of data extraction, transformation, and replication across heterogeneous systems. It’s crucial for maintaining data consistency and supporting real-time data movements.

Oracle GoldenGate Management Pack:
Enhances the manageability of GoldenGate environments by providing automation, monitoring, and optimization tools. This component is particularly valuable in large-scale deployments where manual management would be complex and time-consuming.

Oracle GoldenGate Veridata:
Ensures the integrity of data across systems by comparing and validating replicated data. This technique is especially useful when data accuracy is critical, such as financial reporting or regulatory compliance.

Oracle GoldenGate Studio:
With its visual interface, this component simplifies the setup and management of GoldenGate environments, making it easier to design and deploy data replication processes. This component is ideal for organizations looking to reduce the complexity of managing their data integration projects.

Oracle GoldenGate Monitor:
Provides ongoing surveillance of GoldenGate processes, ensuring that issues are promptly detected and addressed. This component is essential for maintaining the reliability and availability of data replication services.

Oracle GoldenGate Licensing

Licensing Requirements for Source and Target Databases

When deploying Oracle GoldenGate, it is essential to license both the source and target databases involved in data replication.

This dual licensing requirement ensures that all transactional data movements between databases are legally covered.

Whether using Oracle databases or integrating with non-Oracle databases, proper licensing of all endpoints in the data flow is mandatory to comply with Oracle’s licensing policies.

Overview of Named User Plus and Processor Metrics

Oracle GoldenGate offers two primary licensing metrics: Named User Plus (NUP) and Processor.

• Named User Plus (NUP): This metric is based on the number of individuals authorized to use Oracle GoldenGate. Anyone who accesses the software, whether directly or indirectly, must be counted. The NUP metric is often more cost-effective for environments with limited users.
• Processor: The processor metric is determined by the number of processors in the server where Oracle GoldenGate is installed and running. It does not matter how many users access the software; the licensing cost is tied to the hardware capacity. This metric is advantageous for organizations with many users or large-scale deployments.

Processor Metric License Fee Details

For organizations opting for the processor metric, the licensing fee for Oracle GoldenGate is set at $17,500 per processor.

This cost reflects the capacity-based nature of the processor metric, ensuring that the licensing fee scales with the computing power utilized.

Organizations must accurately count and report the number of processors to avoid under-licensing or non-compliance issues.

By understanding these licensing metrics and their respective costs, organizations can make informed decisions about the most cost-effective and compliant way to deploy Oracle GoldenGate in their environments.

Proper licensing ensures legal compliance and enhances data replication processes’ operational efficiency and scalability.

Oracle GoldenGate, only (a) the users of the Oracle database from which you capture data and (b) the users of the Oracle database where you will apply the data must be counted to determine the number of licenses required

Explanation of Named User Plus Metrics

The Named User Plus (NUP) metric is a user-based licensing model. Organizations must license Oracle GoldenGate based on the number of individuals accessing the software.

This includes direct users (who interact with the software) and indirect users (who benefit from its functionality through other applications or systems).

Each named user must be counted, and there is a minimum user requirement for each database instance, ensuring that even small deployments are adequately licensed.

The NUP metric is particularly suitable for environments with limited users, offering a more cost-effective solution than processor-based licensing.

Explanation of Processor Metrics

The Processor metric is a capacity-based licensing model. It requires licensing Oracle GoldenGate based on the number of processors in the servers where the software is installed and running.

Unlike the NUP metric, the Processor metric does not depend on the number of users. Instead, it focuses on the computational capacity available to run Oracle GoldenGate.

This metric is ideal for large-scale deployments with numerous users or high transaction volumes, as it simplifies the licensing process by eliminating the need to count individual users.

Detailed Comparison of Both Licensing Metrics

• User Count vs. Capacity:
  • NUP licenses are based on the number of users.
  • Processor licenses are based on the server’s processing power.
• Cost Efficiency:
  • NUP is more cost-effective for environments with fewer users.
  • Processor metrics can be more efficient for large-scale, high-usage environments.
• Scalability:
  • NUP may require frequent adjustments as user numbers change.
  • Processor metrics remain constant regardless of user count, simplifying scaling.
• Minimum Requirements:
  • NUP has minimum user requirements for each database instance.
  • Processor metric requires accurate processor counts for compliance.

Oracle Active Data Guard

Inclusion in Oracle GoldenGate Licenses

Oracle Active Data Guard is automatically included in Oracle GoldenGate licenses. This inclusion ensures that users can leverage the enhanced data protection and availability features Active Data Guard provides without needing separate licenses.

This integration simplifies the licensing process and provides additional value to organizations using Oracle GoldenGate.

Licensing Requirements and Benefits

With Oracle Active Data Guard included in the Oracle GoldenGate license, there are no additional licensing requirements for using Active Data Guard features.

This inclusion provides several benefits:

• Enhanced Data Protection: Ensures real-time data protection and disaster recovery.
• High Availability: Supports failover and switchover capabilities to minimize downtime.
• Simplified Licensing: Eliminates the need for separate licenses, reducing administrative overhead.

No Separate Licensing Needed

Organizations using Oracle GoldenGate can use Active Data Guard’s capabilities without additional licensing costs.

This benefit streamlines the deployment process and ensures users can access comprehensive data replication and protection features within a single licensing framework.

Oracle Golden Gate Licensing for non-Oracle Database

Licensing Requirements for Non-Oracle Databases

Specific licensing requirements must be met when using Oracle GoldenGate for non-Oracle databases.

These requirements ensure that data replication between non-Oracle and Oracle databases is legally compliant and properly licensed.

Users of the Non-Oracle Database

For licensing Oracle GoldenGate with non-Oracle databases, organizations must count all users who access the non-Oracle database.

This includes:

• Direct Users: Individuals who directly interact with the non-Oracle database.
• Indirect Users: Individuals who indirectly benefit from the data processed by Oracle GoldenGate.

Processors Running the Non-Oracle Database

In addition to user-based licensing, organizations must consider processor-based licensing for non-Oracle databases.

This involves counting:

• Processors at the Source Database: The processors running the non-Oracle database from which data is captured.
• Processors at the Target Database: The processors running the non-Oracle database where data is applied.

Specific Considerations for Non-Oracle Database Environments

When licensing Oracle GoldenGate for non-Oracle databases, organizations should take into account the following considerations:

• Different Licensing Products: Ensure the correct Oracle GoldenGate product is used for non-Oracle databases.
• Accurate Processor Counts: Properly count the processors to avoid under-licensing.
• User Access Management: Maintain accurate records of all users accessing the non-Oracle databases to ensure compliance.

By understanding these specific requirements and considerations, organizations can effectively manage their Oracle GoldenGate licenses for non-Oracle databases, ensuring compliance and optimizing their data replication strategies.

Common reasons for being out of compliant with Oracle GoldenGate

Using GoldenGate for Non-Oracle Databases Without Proper Licenses

One of the most frequent compliance issues is using Oracle GoldenGate for non-Oracle databases without obtaining the appropriate licenses.

Organizations often overlook the fact that different GoldenGate products are required for non-Oracle databases.

Failing to license these environments correctly can have significant legal and financial consequences. It is essential to ensure that all non-Oracle databases involved in data replication are properly licensed according to Oracle’s guidelines.

Failing to License Both Source and Target Databases

Another common compliance pitfall is not licensing both the source and target databases. Oracle GoldenGate requires licenses for all endpoints involved in data capture and application.

Some organizations mistakenly believe licensing only the source or the target database is sufficient. This oversight can lead to non-compliance issues, resulting in unexpected costs and potential service disruptions.

Miscalculating the Core Factor Table

Accurate calculation of the core factor table is crucial for compliance with Oracle licensing policies.

The core factor table determines the number of processor licenses required based on the hardware configuration.

Misunderstanding or miscalculating this table can lead to either over-licensing or under-licensing. Both scenarios can be costly: over-licensing results in unnecessary expenses, while under-licensing exposes the organization to compliance risks and penalties.

Not Understanding Oracle Licensing Rules and Policies

A thorough understanding of Oracle’s licensing rules and policies is essential to maintain compliance. Oracle’s licensing framework can be complex, with specific requirements for different environments and use cases.

Organizations that do not invest the time to fully understand these rules often inadvertently violate licensing terms. Regular training and consultation with licensing experts can help ensure the organization stays compliant and avoids costly mistakes.

Frequently asked questions.

Read more about our Oracle License Management Services.

Do you want to know more about our Oracle License Management Services?

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit