specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Oracle Database
providerId: oracle-database
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Database
  - Oracle
  - Rate Limiting
notes: Oracle Database is on-prem / cloud software, not a hosted public API. Throughput is bounded by
  the licensed processor count, the Resource Manager configuration, and (when accessed via REST through
  ORDS) the ORDS connection pool and database settings. There are no upstream-published per-second numeric
  limits.
description: 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.
sources:
  - https://docs.oracle.com/en/database/oracle/oracle-database/
  - https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/
responseCodes:
  throttled: 429
  unavailable: 503
  conflict: 409
limits:
  - name: Database Resource Manager
    scope: database/consumer-group
    metric: varies
    limit: configured per consumer group
    notes: CPU%, parallel servers, undo, idle time, etc. — operator-defined.
  - name: Session resource limits
    scope: session
    metric: varies
    limit: SESSIONS_PER_USER, CPU_PER_SESSION, etc.
  - name: ORDS connection pool
    scope: ORDS instance
    metric: concurrent_connections
    limit: jdbc.MaxLimit (operator-set)
  - name: Autonomous Database (cloud)
    scope: instance
    metric: ECPU
    limit: bounded by instance shape and auto-scale
policies:
  - name: Resource Manager
    description: Use Oracle Database Resource Manager to allocate CPU / IO / parallelism across consumer
      groups; this is the primary throughput-shaping mechanism.
  - name: ORDS tuning
    description: For REST traffic, size jdbc.MaxLimit and jdbc.InitialLimit to match expected concurrency.
  - name: Backoff
    description: Honor 429 / 503 from cloud-managed services; for ORA- errors (e.g. ORA-04031, ORA-00018),
      apply application-level backoff.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com