RE: Intermittent ORA-12516 ( TNS:listener could not find available handler with matching protocol stack)
- From: "Powell, Mark" <mark.powell2@xxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 8 Jul 2014 16:17:58 +0000
We had this error, ORA-12516, recently and we also came nowhere near our
maximum allowed number of sessions and/or processes.
We noticed the service for java was showing blocked. Reloading would clear the
issue but it would come back in an hour and then later in quicker intervals.
Bouncing the listener seems to have cleared up the problem as we have ran over
two weeks without the error returning.
We did however take some other action as we noticed that our listener.log was
over 2G in size and growing by 20 error messages a second so we turned off
logging and removed the file before we bounced the listener. Since you are on
11.2 you should not be subject to the connection errors that Oracle admits are
possible pre-11g when the listener.log exceeds 2G, but if your listener.log is
over 2G I suggest you remove it.
Rodrigo Mufalani from this list was kind enough to provide me an Oracle support
reference for this little pre-11g fact: (See #3)
Listener Hanging - Information to Get For Resolving or Troubleshooting (Doc ID
230156.1)
The note might be helpful with 11g+ and then again Oracle fixes do not always
completely fix the underlying problem so maybe this may still be true in 11.2.
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of David Barbour
Sent: Monday, July 07, 2014 3:43 PM
To: frasebook4@xxxxxxxxx
Cc: oracle-l mailing list
Subject: Re: Intermittent ORA-12516 ( TNS:listener could not find available
handler with matching protocol stack)
What is the operating system?
On Fri, Jul 4, 2014 at 10:07 AM, nico torres
<frasebook4@xxxxxxxxx<mailto:frasebook4@xxxxxxxxx>> wrote:
Hi guys,
JDBC Connections to my 11.2.0.4 Database are getting this error quite
intermittently:
TNS-12516: TNS:listener could not find available handler with matching protocol
stack
I am asking you because I researched quite a lot about this error, and all
solutions say this is a number of processes/sessions, but this is not the case,
since sessions/processes number is quite low, and far from the maximum.
I searched in the listener.log, and only found "Warning: Subscription For Node
Down Event Still Pending" warnings, and solved them setting
SUBSCRIBE_FOR_NODE_DOWN_EVENT=OFF, but it had nothing to do with the error,
because it keeps showing up.
Couldn't find any more information on the listener.log, only the same errors
JDBC connections are getting (TNS-12516: TNS:listener could not find available
handler with matching protocol stack)
Any ideas?
Thanks a lot.
Other related posts:
