// Oracle error reference

ORA-00018: maximum number of sessions exceeded

The instance already has as many sessions as the SESSIONS parameter allows, so new connections and recursive sessions are refused.

Error code
ORA-00018
Category
Space, memory and limits
Error message
maximum number of sessions exceeded

What it means

The SESSIONS initialization parameter caps the number of sessions in the instance, including background and recursive sessions. ORA-00018 means that cap is reached.

Common causes

  • Connection pools that open more connections than planned, or leak them.
  • A SESSIONS value too low for the workload.
  • Many idle sessions left connected by clients.

How to fix it

  1. Check current usage against the limits.

    SELECT resource_name, current_utilization, max_utilization, limit_value
    FROM v$resource_limit WHERE resource_name IN ('sessions', 'processes');
  2. Cap application pool sizes and close idle connections.

  3. Raise the limit if needed (takes effect after restart).

    ALTER SYSTEM SET sessions = 1500 SCOPE = SPFILE;

Related errors

More space, memory and limits errors

The code and message text are from the Oracle Database Error Help. Browse the full Oracle error list or search every database error.

// fewer errors, faster fixes

Work on Oracle in SQLly

A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for Oracle and the other databases you use.