Oracle Essbase · Rate Limits
Oracle Essbase Rate Limits
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.
2 Limits
AnalyticsOLAPOracle CloudRate Limiting
Limits
Concurrent Sessions (configurable) instance
see Essbase configuration
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.
REST API Requests instance
bound by OCI compute shape
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
Capacity-Bound Throttling
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.
Backoff Strategy
Clients should implement exponential backoff with jitter on 5xx responses; honor any Retry-After header when present.
Session Management
Long-running calc, MaxL, or query operations should reuse authenticated sessions rather than re-authenticating per request to avoid exhausting session-pool capacity.