You can get this error if you have maxed out available processes/sessions on the database. Check the alert.log for either of those errors. There are a variety of situations that can spawn large number of processes on your system when the regular number of processes/sessions appears to be low, like default parallelism on a query and as explained in this note Intermittent TNS-12516 or TNS-12519 Errors When Connecting Via Oracle Net (Doc ID 240710.1) there can be a lag as to when the listener determines the instance is overwhelmed versus what the reality may be. Also the parallelism as mentioned based on bad parallel value settings can cause the spawning of a large amount of parallel processes. In one example query I ran into on a system recently, it was spawning 1024 parallel processes. ----- Original Message ----- From: "nico torres" <frasebook4@xxxxxxxxx> To: oracle-l@xxxxxxxxxxxxx Sent: Friday, July 4, 2014 8:07:55 AM Subject: Intermittent ORA-12516 ( TNS:listener could not find available handler with matching protocol stack) 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.