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 Essbase
providerId: oracle-essbase
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:
  - Analytics
  - OLAP
  - Oracle Cloud
  - Rate Limiting
description: >-
  Oracle Essbase does not publish per-second or per-minute API rate limits in
  its REST API documentation. Throttling, when present, is governed by the
  underlying OCI compute capacity (OCPU and memory of the Essbase host) and
  by Essbase's own session, query, and calc concurrency settings configured
  per service instance. Customers can size and tune limits at deployment time
  rather than relying on a multi-tenant published rate.
sources:
  - https://docs.oracle.com/en/database/other-databases/essbase/
  - https://docs.oracle.com/en/database/other-databases/essbase/21/essoa/index.html
notes: >-
  No public per-tier RPS/RPM numbers are published. Limits are effectively the
  capacity of the deployed OCI compute shape plus Essbase's configurable
  session, calculation, and query limits. Set reconciled to true after
  capturing instance-specific tuning values.
responseCodes:
  unauthorized: 401
  forbidden: 403
  notFound: 404
  serviceUnavailable: 503
limits:
  - name: Concurrent Sessions (configurable)
    scope: instance
    metric: concurrent_sessions
    limit: see Essbase configuration
    notes: >-
      Configured per Essbase application via NETDELAY, NETRETRY, and
      session/connection settings. Default Essbase server limits are tuned at
      provisioning time, not exposed through a public per-tier API rate.
  - name: REST API Requests
    scope: instance
    metric: varies
    limit: bound by OCI compute shape
    notes: >-
      Throughput is bound by the OCPU count and memory of the underlying OCI
      compute shape running the Essbase instance, not by a separate public
      rate-limit policy.
policies:
  - name: Capacity-Bound Throttling
    description: >-
      Throughput limits are determined by the OCI compute shape (OCPU,
      memory) and configurable Essbase session, query, and calc concurrency
      settings rather than a published multi-tenant rate-limit table.
  - name: Backoff Strategy
    description: >-
      Clients should implement exponential backoff with jitter on 5xx
      responses; honor any Retry-After header when present.
  - name: Session Management
    description: >-
      Long-running calc, MaxL, or query operations should reuse authenticated
      sessions rather than re-authenticating per request to avoid exhausting
      session-pool capacity.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com