Home » RDBMS Server » Networking and Gateways » TNS-12518: TNS:listener could not hand off client connection (inbound connection timed out (ORA-3136))
TNS-12518: TNS:listener could not hand off client connection [message #391533] Thu, 12 March 2009 08:23 Go to next message
oraclevijay
Messages: 10
Registered: November 2008
Junior Member
Hi Every body,

I am facing a problem in oracle production database.I got the below error messages in listener.log
TNS-12571: TNS:packet writer failure
TNS-12560: TNS:protocol adapter error
Shocked
TNS-12571: TNS:packet writer failure
TNS-12560: TNS:protocol adapter error

TNS-12518: TNS:listener could not hand off client connection
WARNING: Subscription for node down event still pending
the tns-12518 repeatly coming
also getting the follwoing error in alert log
WARNING: inbound connection timed out (ORA-3136)

Immediate Kill Session#: 242, Serial#: 2229
Immediate Kill Session: sess: 765A9FF4 OS pid: 3252
Immediate Kill Session#: 255, Serial#: 2809
Immediate Kill Session: sess: 765BA2BC OS pid: 8188 .......
......
...........

my oracle database configuration is
oracle 10.2.0.4 WINDOWS

RAM 8 GB
ORACLE USAGE 1.324GB
available free physical memory 6gb
only one database installed in server.


os MICROSOFT WINDOWS SERVER 2003 R2 ENTERPRISE EDITION SERVICE PACK 2

SERVER DEDICATED
DIRECT_HANDOFF_TTC=off
server has intial 3gb and maximun 4gb virutal memory

sga_target='1100M'
pga_aggregate_target='750M'
sessions=335
processes=300

default status is arround 65 -75 sessions are connected to the database.
"my thought:" when number of sessions increased to 100 or something.. it is puting the error."
I have increased the virutual memory. "
what can i do furthur ......

please,give me the solution
Thanks in Advance
Vijay.S
Re: TNS-12518: TNS:listener could not hand off client connection [message #391561 is a reply to message #391533] Thu, 12 March 2009 10:23 Go to previous message
Michel Cadot
Messages: 59422
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-03136: inbound connection timed out
 *Cause:  Inbound connection was timed out by the server because
          user authentication was not completed within the given time
          specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
 *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections.
          2) Configure SQL*NET with a proper inbound connect timeout value
             if necessary.


Regards
Michel
Previous Topic: Listener issue on Windows
Next Topic: db links not working
Goto Forum:
  


Current Time: Thu Oct 23 08:27:53 CDT 2014

Total time taken to generate the page: 0.08233 seconds