Oracle Cloud Infrastructure GoldenGate is a fully managed, native cloud service that moves data in real-time, at scale. OCI GoldenGate processes data as it moves from one or more data management systems to target databases. You can also design, run, orchestrate, and monitor data replication tasks without having to allocate or manage any compute environments.
Oracle Cloud Infrastructure GoldenGate Concepts
The following concepts are essential for working with the GoldenGate service.
- Compartment: Organizes and isolates your cloud resources, such as cloud networks, compute instances, block volumes, or OCI GoldenGate deployments, and database registrations. Only users with permission to a compartment can work with the resources within that compartment. Compartments also serve as a security boundary inside OCI GoldenGate. Only deployments and database registrations within the same compartment can access each other.
- Deployment: A container for your OCI GoldenGate resources, such as the OCI GoldenGate Deployment Console.
- Deployment Backup: A backup of a deployment's current state, retained for 60 days. It can be used to restore a deployment or create a new deployment with the state of the original deployment at the time the backup was taken.
- Database Registration: Captures source and target credential information and enables networking between the OCI GoldenGate service tenancy virtual cloud network (VCN) and your tenancy VCN using a private endpoint. A database registration contains the connectivity information to source or target end points.
- Extract: A process that runs against the source database and extracts, or captures data.
- Trail: A series of files on the source, intermediary, and/or target system where Oracle GoldenGate stores the captured changes to support the continuous extraction and replication of database changes.
- Replicat: A process that delivers data to a target database. It reads the trail file on the target database, reconstructs the DML or DDL operations, and applies them to the target database.
For more information about Oracle GoldenGate concepts, see Components of the Oracle GoldenGate Microservices Architecture.
Accessing Oracle Cloud Infrastructure
Most types of Oracle Cloud Infrastructure resources have a unique, Oracle-assigned identifier called an Oracle Cloud ID (OCID).
For information about the OCID format and other ways to identify your resources, see Resource Identifiers.
Creating a quota limit lets you limit the number of deployment resources in a compartment.
set goldengate quota deployment-count to 5 in compartment <compartment_name>
Metering and Billing
Metering and billing for OCI GoldenGate is based on the number of OCPUs the service uses per minute.
When you create an OCI GoldenGate deployment, you select the number of OCPUs between 1 and 24 that your deployment will use. Each OCPU allocates an additional 16 GB memory.
You can enable auto scaling, which allows the service to scale up to three times the OCPU Count you specified upon creation. When you enable auto scaling, you are billed for the actual average number of OCPUs consumed per hour.
For example, if you specify 3 as the base OCPU and enable Auto Scale, then the total OCPUs that can be used is 9. When the OCPU Utilization is greater than 33.333% of 9 OCPUs, you are billed for the integer value over 33.333%, which is 4 OCPUs.
|OCPU Utilization Greater than||OCPU Utilization Less than or equal to||Billed for|
OCI GoldenGate cannot scale over 24 OCPUs, which is the maximum number of OCPUs. For example, if you select 9 OCPUs as your base OCPU Count and enable Auto Scale, the service will scale up to 24 OCPUs. You can enable or disable auto scaling at any time. Learn more about Scaling a Deployment.
You can monitor the OCPU consumption and memory of a deployment in the Metrics section of a deployment's Detail page.
The GoldenGate service is integrated with various Oracle Cloud Infrastructure services and features.
OCI GoldenGate integrates with the Identity and Access Management (IAM) service for authentication and authorization for the Console, SDK, CLI, and REST API, but not the OCI GoldenGate Deployment Console. To access the OCI GoldenGate Deployment Console, use the username and password that you specify when you create the deployment.
To learn more about the OCI GoldenGate Deployment Console, see Replicating Data.
To learn more about IAM, see IAM Overview.
OCI GoldenGate is not integrated with the common Work Requests API. The GoldenGate service uses its own API for Work Requests. See Work Request Reference.
Oracle Cloud Infrastructure Monitoring lets you actively and passively monitor your Oracle Cloud Infrastructure GoldenGate resources and alarms. Oracle Cloud Infrastructure GoldenGate Metrics captures CPU utilization, OCPU consumption, memory utilization, deployment health, and inbound and outbound lag. You can view these metrics using the Monitoring service, or on your Deployment Details page.