Re: TNS-12537 after starting listener after upgrade from 10.2.0.2. 10.2.0.4

Comments embedded.
On Aug 11, 9:34 am, sfa..._at_gmail.com wrote:
> Hello, I have upgraded 7 Unix Solaris 5.10  Boxes from 10.2.0.2 to
> 10.2.0.4 and applied recommend patches.  All upgrades worked with the
> exception of one server.  One server won't start the listener.  I get
> the following:
> 35% lsnrctl start
>
> LSNRCTL for Solaris: Version 10.2.0.4.0 - Production on 11-AUG-2008
> 10:17:31
> Copyright (c) 1991, 2007, Oracle.  All rights reserved.
> Starting /oracle/BWD/102_64/bin/tnslsnr: please wait...
> TNS-12537: TNS:connection closed
>  TNS-12560: TNS:protocol adapter error
>   TNS-00507: Connection closed
>    Solaris Error: 29: Illegal seek
>
> I have searched google.com and the only thing I can find is related to
> Oracle 8 and Windows:
> add 127.0.0.1       localhost.(domain) localhost to /etc/hosts.
>
> I did this with no luck.
>

But, this is a Solaris error regarding the failure of an lseek call through a pipe.

> I have two instances of Oracle on this one machine.  

I expect that you mean you have two INSTALLATIONS of Oracle on this machine.

> One listener
> works, the other doesn't.
> I have done the following :
> cd $ORACLE_HOME/bin
> ./relink all
>
> then:
> cd $ORACLE_HOME/network/lib
> make -f ins_network.mk install
> make: Fatal error: Can't find `ins_network.mk': No such file or
> directory
>

That's because you need to use int_net_server.mk.

> The port used by the listener is 1521 and netstat -an |grep 1521
> reports port not in use.
>

The listener isn't running, so I would expect port 1521 to not be in use.

> I've changed listener.ora with tracing and nothing seems obvious.
> trace_level_listener = 16
> trace_file_listener = listener
> trace_timestamp_listener = on
> trace_filelen_listener = 100
> trace_fileno_listener = 2
> log_file_listener=listener
>

I would suggest you invoke truss and save the output to a file:

$ truss lsnrctl start > lsnrctl.out 2>&1

and see where the offending lseek call is failing. This being the result of an operating system error it's where you should start looking for answers.

> -- Steve

David Fitzjarrell Received on Mon Aug 11 2008 - 11:56:01 CDT