Oracle Database · Rate Limits

Oracle Database Rate Limits

Oracle Database does not impose a global rate limit. Operators tune throughput via Database Resource Manager (CPU / IO / parallel server limits), session-level resource limits, and (for REST access) ORDS pool sizing. Cloud-managed variants (Autonomous DB, Base Database Service) inherit OCI service-level throttling, surfaced as 429 / 503 with Retry-After.

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

It captures 4 rate-limit definitions, measuring varies, concurrent_connections, and ECPU.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, unavailable, and conflict.

Tagged areas include Database, Oracle, and Rate Limiting.

4 Limits Throttle: 429
DatabaseOracleRate Limiting

Limits

Database Resource Manager database/consumer-group
varies
configured per consumer group
CPU%, parallel servers, undo, idle time, etc. — operator-defined.
Session resource limits session
varies
SESSIONS_PER_USER, CPU_PER_SESSION, etc.
ORDS connection pool ORDS instance
concurrent_connections
jdbc.MaxLimit (operator-set)
Autonomous Database (cloud) instance
ECPU
bounded by instance shape and auto-scale

Policies

Resource Manager
Use Oracle Database Resource Manager to allocate CPU / IO / parallelism across consumer groups; this is the primary throughput-shaping mechanism.
ORDS tuning
For REST traffic, size jdbc.MaxLimit and jdbc.InitialLimit to match expected concurrency.
Backoff
Honor 429 / 503 from cloud-managed services; for ORA- errors (e.g. ORA-04031, ORA-00018), apply application-level backoff.

Sources