Resolving ORA-12518: TNS:listener Could Not Hand off Client Connection Error

milly 1:12 pm on March 29, 2010 | Answers: 1    
Tags: client (3), connection (8), database (51), listener, oracle (136), process (7), server (37)

Rate Knowledge: (1 votes)

 Loading ...

• milly 1:12 pm on March 29, 2010
  

  To troubleshoot, follow the tips below:

  1. Find out if it’s a global issue (Apply to all client machines), or it is an isolated issue. (Apply to only one or few client machines)
  If it is an isolated issue, then focus your troubleshooting on the tnsnames.ora and sqlnet.ora files on the client’s machine.

  2. Check your client’s tnsnames.ora file, make sure SERVICE_NAME matches the one that’s being setup on the server’s listener:
  For example, in one situation,
  the following tnsnames entry would throw ORA-12518 error:

  GISDB1 =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = GISDB1)(PORT = 1521))
      (CONNECT_DATA =
        (SERVER = DEDICATED)
        (SERVICE_NAME = gisdb1)
      )
    )

  After troubleshooting, the correct SERVICE_NAME entry should be:

  GISDB1 =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = GISDB1)(PORT = 1521))
      (CONNECT_DATA =
        (SERVER = DEDICATED)
        (SERVICE_NAME = gisdb1.domain.net)
      )
    )

  3. Check whether your listener version is compatible with database. The general rule is to use always same or higher version of listener.

  4. Check if local connection as sysdba is successful

  5. Check the DB Processes is reached it’s limit

  6. If you’re running Windows DB, make sure the tnsnames service is started