Oracle Database 19c · Rate Limits

Oracle Database 19C Rate Limits

Oracle Database 19c throughput is operator-controlled via Database Resource Manager, session resource limits, and (for REST) ORDS pool configuration. Cloud-managed 19c (Autonomous DB, Base Database Service) inherits OCI throttling — 429 / 503 with Retry-After.

Oracle Database 19C Rate Limits is the machine-readable rate-limit profile for Oracle Database 19c 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
Session resource limits session
varies
SESSIONS_PER_USER, CPU_PER_SESSION (operator-set)
ORDS connection pool ORDS instance
concurrent_connections
jdbc.MaxLimit (operator-set)
Autonomous Database 19c instance
ECPU
instance-shape-bounded

Policies

Resource Manager
Primary throughput-shaping mechanism — allocate CPU / IO / parallelism per consumer group.
ORDS tuning
Size connection pool to match expected concurrency for REST endpoints.
Backoff
Honor 429 / 503 from cloud services; ORA- errors handled with application-level retry.

Sources