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
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
SESSIONSvalue too low for the workload. - Many idle sessions left connected by clients.
How to fix it
-
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'); -
Cap application pool sizes and close idle connections.
-
Raise the limit if needed (takes effect after restart).
ALTER SYSTEM SET sessions = 1500 SCOPE = SPFILE;
Related errors
ORA-00020maximum number of processes exceededORA-12519TNS: no appropriate service handler found1040MySQL: Too many connections53300PostgreSQL: too many connections
More space, memory and limits errors
ORA-01652unable to extend temp segmentORA-01653unable to extend table in tablespaceORA-01950no privileges on tablespaceORA-01555snapshot too oldORA-30036unable to extend segment in undo tablespaceORA-04031unable to allocate bytes of shared memoryORA-01000maximum open cursors exceededORA-00257archiver error
The code and message text are from the Oracle Database Error Help. Browse the full Oracle error list or search every database error.
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.