The reason why the listener cannot be started in Oracle. TNS-12537: TNS: Connection closed

 

Original address: http://space.itpub.net/index.php? Action/viewspace/Itemid/84958 symptoms

The listener fails to start with the following errors:
TNS-12537: TNS: Connection closed
TNS-12560: TNS: protocol adapter Error
TNS-00507: Connection closed
Linux error: 29: Illegal seek
Generic to UNIX platforms.

Cause

Wrong syntax in hosts file and also due to the tnslsnr process was enhanced in

10.1.0.3 to support fan (Fast Application Notification)
ONS (Oracle Notification Services). This new code opens a socket open on localhost. Therefore
"Localhost" shocould be defined on the system.

This new code opens a socket open on localhost. Therefore "localhost" shocould be defined on
System.

Fix

Change/etc/hosts file to include
127.0.0.1 localhost. localdomain localhost

Applies:

Oracle Net Services-version: 10.1.0.0 to 10.2.0.2
This problem can occur on any platform.

Symptoms

Unable to start an Oracle10g r1 (or R2) TNS listener on UNIX:

For example:

$ LSNRCTL start
LSNRCTL For HPUX: Version 10.1.0.4.0-production on 01-jul-2005 10:16:59
Copyright (c) 1991,200 4, Oracle. All rights reserved.
Starting/DB02/product/10.1/bin/tnslsnr: Please wait...
TNS-12537: TNS: Connection closed
TNS-12560: TNS: PROTO adapter Error
TNS-00507: Connection closed
HPUX error: 29: Illegal seek

Changes

Verify the user attempting to start the TNS listener process has read permissions on the/etc/hosts file, and that this file contains the localhost entry:

127.0.0.1 localhost. localdomain localhost
192.168.2.20 prfinders.us.oracle.com prfinders.

Cause

TNS Listener fails while attempting to initiate sublistener to ONS node down event.

Level 16 TNS Listener trace shows the last action:

...
[01-jul-2005 10: 16: 59: 727] nsglonsinit: initiated submodules for node down event
...

Same symptoms and corrective action found in bug 4227455 ocs_main_solaris_050304-unable to start the second listener of if OS user is unable to read the/etc/hosts file.

Solution

To implement the solution, Please execute the following steps:

1. explicitly disable the 10g TNS Listener's subscrition to ONS by editing the listener. ora file and add the parameter below:

Subscribe_for_node_down_event _ <listener_name> = off

Where <listener_name> wocould be replaced with the actual listener name configured in the listener. ora file.

For example, if the listener name is listener (default), the parameter wocould be:

Subscribe_for_node_down_event_listener = off

-Save the listener. ora File

2. Start the TNS listener from a new LSNRCTL prompt:

LSNRCTL <return>

LSNRCTL> Start