ORA-00020: maximum number of processes exceeded
The instance reached its PROCESSES limit, so it can't start a server process for a new connection. Usually too many connections from pools.
- Error code
ORA-00020- Category
- Space, memory and limits
What it means
With dedicated servers each connection uses an operating-system process, and the PROCESSES parameter caps how many the instance may have. ORA-00020 means that cap is reached; the full 19c message is maximum number of processes (string) exceeded. Often even administrators can't connect normally.
Common causes
- Connection pools or applications opening more connections than the limit, or leaking them.
- A
PROCESSESsetting too low for the number of users.
How to fix it
-
Check usage.
SELECT resource_name, current_utilization, max_utilization, limit_value FROM v$resource_limit WHERE resource_name = 'processes';
-
Reduce connections: cap pool sizes, close idle sessions, or use shared servers or DRCP for many short connections.
-
Raise the limit and restart.
ALTER SYSTEM SET processes = 1000 SCOPE = SPFILE;
Related errors
ORA-00018maximum number of sessions 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.