ORA-12519: TNS: no appropriate service handler found
The listener has no handler ready to take a new connection for the service, very often because the database has reached its PROCESSES limit.
- Error code
ORA-12519- Category
- Connection and login
What it means
The listener hands each new connection to a service handler. ORA-12519 means none was available, and a common reason is that the instance is at its PROCESSES limit, so the listener marks the dedicated handler as blocked. The listener's view can lag a little behind the database, so the error can also appear in bursts when many connections arrive at once.
Common causes
- The database is at or near
PROCESSES(see ORA-00020). - A burst of new connections from an application pool starting up.
- The service isn't fully registered with the listener.
How to fix it
-
Check process usage and raise
PROCESSESif needed.SELECT resource_name, current_utilization, limit_value FROM v$resource_limit WHERE resource_name = 'processes';
-
Limit how many connections pools open, and how fast they open them.
-
Run
lsnrctl servicesto see each handler's state (readyorblocked).
Related errors
ORA-00020maximum number of processes exceededORA-00018maximum number of sessions exceededORA-12514TNS: listener doesn't know the requested serviceORA-12541TNS: no listener
More connection and login errors
ORA-01017invalid username/password; logon deniedORA-12154TNS: could not resolve the connect identifierORA-12505TNS: listener doesn't know the SIDORA-12170TNS: connect timeout occurredORA-03113end-of-file on communication channelORA-03135connection lost contactORA-28000the account is lockedORA-28001the password has expired
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.