This content has been marked as final. Show 14 replies
In most cases it's a network problem. On HP-UX it can be a bug.
What version of Oracle are you using and what platform?
I am using Oracle 10g XE on Windows Platform
Check your EventLog for errors regarding network connections and check the alert log of your database. You can also get this error when your database crashed.
Check the status of oracle service in windows services.
there u can find the service by name OracleInstancename.
ORA-12518: TNS:listener could not hand off client connection
Your server is probably running out of memory and need to swap memory to disk.
One cause can be an Oracle process consuming too much memory.
A possible workaround is to set following parameter in the listener.ora and restart the listener:
You might need to increase the value of large_pool_size.
we have to configure Large pool size also if SGA is automatic management or not?
My experience with this error has shown an out of memory condition exists.
I have this problem when DBcontrol is running on same server as database instance. Working with Oracle Support for several weeks, no resolution to date. So much for opening a Oracle Service Prayer (Request)
Include the parameter outside the paranthesis.
where do I put DIRECT_HANDOFF_TTC_LISTENER=OFF inThis is a syntax question. As usual, the syntax is described completely and accurately in an Oracle reference manual.
In this case it is found in the List of Books found at http://www.oracle.com/pls/db102/portal.portal_db?selected=3 for 10gR2. The book you are looking for is the "Net Services Reference". And the recommended reading starts in Chapter 3 ("Syntax Rules for Configuration Files") and continues in Chapter 7 ("Listener Parameters (listener.ora)")
Not everyone has time to pick up a book and thumb through pages looking aimlessly for a solution they have no idea exists or where to find it if it does.
Isn't that the point of a forum? To ask questions and collaborate? Forgive him for using this forum for its intended purpose...
Anyway, I too am getting this error -- our export job was about to kick off this morning when all of a sudden the listener encountered some sort of problem. I checked now and our processes are set to 900 yet they are only at 145 now (the database restarted automatically as normal about 2 hours ago, so the processes haven't gotten too high yet).
Could it be taht the processes really did get too high though? I don't see any indications that this server was out of memory... it does nothing but run this single database and it has 4GB of RAM.
this problem almost root cause of limited server resources or configuration. try to check these
1. database server memory were enough for new connection
2. database connection parameters such as
2.1 dedicated server, pls checked processes parameter or query from v$resource_limit where resource_name=’processes’; checked max_utilization must less than Limit_value or
2.2 shared server, pls verify large_pool_size or check dispatcher were enough for all connection.
3. you may check related log such as listener.log, alert log, trace file, etc
referrence : http://blogitknowledge.u-indy.com/database-services/oracle-troubleshoot/oracle-troubleshoot-ora-12518-tnslistener-could-not-hand-off-client-connection/
I got the same issue, finally it was due to the service of tns was down,
Thanks for the tip.
I stopped the services by using oradim utility and now its' working.
oradim -delete -sid orcl
oradim -new -sid orcl
sqlplus / as sysdba
Hope this helps