Too many TNS connections open simultaneously
Philippe Gamba
the following message :
TNS 12223 : "Too many TNS connections open simultaneously"
Who can tell me about what goes wrong in my application and what to look
for ?
Thanks
--
Philippe GAMBA (SO223) - SEMA GROUP TELECOM
mailto:philipp...@grenoble.sema.fr
Pete Sharman
Error: ORA 12223
Text: TNS:internal limit restriction exceeded
-------------------------------------------------------------------------------
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and re-try.
Explanation:
A layer of the net code has run out of some resource.
Information lower down the error stack may help
identify the resource which is depleted.
Diagnosis:
- Check the error stack for any OS errors
(see sqlnet.log)
The OS errors at in the error stack normally indicate which
resource is depleted.
- You may also need to get client or listener trace output
to see what was happening when the resource was depleted.
- Check the OS kernel parameters for number of processes, file
handles etc.. Eg: NPROC, MAXUPRC, NFILE, NSTREAM
- This message will frequently appear when swap space is exhausted,
Check the memory usage.
- Check for lots of DEFUNCT process in the process listing. These
use up slots in the process table and would indicate a problem.
HTH.
Pete
Philippe Gamba wrote:
--
Regards
Pete
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Pete Sharman Email: psha...@us.oracle.com
Project Manager Phone: +1.650.607.0109 (int'l)
Worldwide Internal Services Education (650)607 0109 (local)
Oracle Corporation
SQL> select standard_disclaimer, witty_remark
2 from company_requirements;
Opinions are mine and do not necessarily reflect those of Oracle
Corporation
"Controlling application developers is like herding cats."
Kevin Loney, ORACLE DBA Handbook
"Oh no it's not! It's much harder than that!"
Bruce Pihlamae, long term ORACLE DBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Philippe Gamba
Here is the sqlnet.log file, if you can help us finding something interesting to learn from it:
***********************************************************************
Fatal OSN connect error 12223, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=/home1/oracle/app/oracle/product/7
.3.4/bin/oracle)(ARGV0=oracleSYN1)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTO
COL=beq)))')(DETACH=NO))(CONNECT_DATA=(CID=(PROGRAM=)(HOST=S1)(USER=synapse))))
VERSION INFORMATION:
TNS for Solaris: Version
2.3.4.0.0 - Production
Oracle Bequeath NT Protocol
Adapter for Solaris: Version 2.3.4.0.0 - Pro
duction
Time: 11-MAI-99 15:52:20
Tracing not turned on.
Tns error struct:
nr err code: 12223
TNS-12223: TNS: restriction
de limite interne dipassie
ns main err code: 12540
TNS-12540: TNS: restriction de limite interne dipassie
ns secondary err code: 12560
nt main err code: 510
TNS-00510: Restriction de limite interne dipassie
and sometimes I've got just after the previous one, the following error trace in the sqlnet.log file, from which I don't know either what to learn:
Fatal OSN connect error 12547, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=/home1/oracle/app/oracle/product/7
.3.4/bin/oracle)(ARGV0=oracleSYN1)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTO
COL=beq)))')(DETACH=NO))(CONNECT_DATA=(CID=(PROGRAM=)(HOST=S1)(USER=synapse))))
VERSION INFORMATION:
TNS for Solaris: Version
2.3.4.0.0 - Production
Oracle Bequeath NT Protocol
Adapter for Solaris: Version 2.3.4.0.0 - Pro
duction
Time: 11-MAI-99 21:50:16
Tracing not turned on.
Tns error struct:
nr err code: 12206
TNS-12206: TNS: erreur TNS
regue pendant la navigation
ns main err code: 12547
TNS-12547: TNS: contact perdu
ns secondary err code: 12560
nt main err code: 517
TNS-00517: Contact perdu
nt secondary err code: 32
nt OS err code: 0
We access the database mostly via RogueWave DbTools++.
Thanks a lot in advance if you can help.
Pete Sharman a écrit :