Oracle GoldenGate · Rate Limits

Oracle Goldengate Rate Limits

Oracle GoldenGate's management REST APIs (Service Manager, Administration Server, Distribution Server, Receiver Server, Performance Metrics Server) do not publish per-second or per-minute rate-limit numbers. Throughput is bound by the OCPU and memory of the GoldenGate deployment, by the configured replication trail throughput, and by the underlying source and target database I/O. The OCI managed service additionally inherits the general OCI control-plane throttling behaviour for resource lifecycle operations.

Oracle Goldengate Rate Limits is the machine-readable rate-limit profile for Oracle GoldenGate on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring varies, requests_per_second, and events_per_second.

The profile also includes 4 backoff/retry policies defined and response codes documented for unauthorized, forbidden, notFound, throttled, and serviceUnavailable.

Tagged areas include CDC, Data Integration, Oracle Cloud, Rate Limiting, and Real-Time Replication.

3 Limits Throttle: 429
CDCData IntegrationOracle CloudRate LimitingReal-Time Replication

Limits

Management REST API Throughput deployment
varies
bound by GoldenGate deployment OCPU
Throughput is governed by the OCPU count of the GoldenGate deployment (managed-service edition or on-premises host) and is not exposed as a separate per-tenancy rate-limit table.
OCI Control-Plane Operations tenancy
requests_per_second
see OCI service-limits documentation
Lifecycle operations against OCI GoldenGate (create, update, scale, delete deployment) inherit the OCI control-plane throttling envelope shared by all OCI services in the tenancy.
Replication Trail Throughput deployment
events_per_second
bound by deployment OCPU and source/target I/O
Sustained replication throughput depends on the GoldenGate deployment sizing, trail file storage, and source/target database I/O capacity.

Policies

Capacity-Bound Throttling
Throughput limits are determined by deployment OCPU, trail storage IO, and source/target database capacity rather than a published per-tenancy rate-limit table.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 / 5xx responses; honor any Retry-After header when present.
Health and Metrics
Use the Performance Metrics Server REST API (or OCI Monitoring for the managed service) for visibility into lag, throughput, and CPU saturation rather than polling the management API at high frequency.
Capacity Adjustment
Scale the deployment OCPU count or migrate to a larger compute shape to lift effective throughput; raise OCI control-plane limits via a service request if needed.

Sources