Hi,
ORA-12516: TNS:listener could not find available handler with matching protocol
Since yesterday error is so frequent in the LISTENER.ORA file of our PROD DB (10.2.0.4) on RHL with ASM instance. grep TNS-12516 wc shows error over seven thousand in the listener.ora.
I read a little that when DB CONNECTIONS reach over DB PROCESSES value, the error can arise in the listener.ora, is it TRUE ??
I just checked the PROCESSES parameter and it is set to 300, also count the current connect session from v$session, and its 171 at the moment. no idea how many connections were connected 3 hours ago (at the time of error alarm).
Please suggest what can be done as a DBA at the DB level to avoid the error.
## An example connection (ESTABLISHED) from Listener.ora with the error:
28-AUG-2012 09:09:11 * (CONNECT_DATA=(SID=1P)(SERVICE_NAME=xx)(CID=(PROGRAM=D:\amgr.EXE)(HOST=IA)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=xxx)(PORT=6x)) * establish * xxx * 12516
TNS-12516: TNS:listener could not find available handler with matching protocol stack
1* select * from v$resource_limit where resource_name IN ('processes','sessions')
RESOURCE_NAME CURRENT_UTILIZATION MAX_UTILIZATION INITIAL_ALLOCATION LIMIT_VALUE
------------------------- ------------------- --------------- -----------------------
processes 190 300 300 300
sessions 193 306 335 335
Thanks a lot in advance.
Best Regards
Edited by: K-Saf on Aug 28, 2012 12:33 PM