Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Listener fails to start

Re: Listener fails to start

From: Helma <helma.vinke_at_hotmail.com>
Date: Sun, 28 Oct 2007 03:54:48 -0700
Message-ID: <1193568888.191262.142800@o38g2000hse.googlegroups.com>


On Oct 28, 11:45 am, Frank van Bortel <frank.van.bor..._at_gmail.com> wrote:
> Helma wrote:
>
> > Frank,
> > the output is as follows:
>
> > [oracle_at_localhost ~]$ lsnrctl start
>
> > LSNRCTL for Linux: Version 9.2.0.1.0 - Production on 27-OCT-2007
> > 12:59:05
>
> > Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
>
> > Starting /home/oracle/product/ora9i/bin/tnslsnr: please wait...
>
> > TNS-12547: TNS:lost contact
> > TNS-12560: TNS:protocol adapter error
> > TNS-00517: Lost contact
> > Linux Error: 32: Broken pipe
> > [oracle_at_localhost ~]$
>
> > and the ip addr::
>
> > [root_at_localhost ~]# ip addr
> > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > inet 127.0.0.1/8 scope host lo
> > inet6 ::1/128 scope host
> > valid_lft forever preferred_lft forever
> > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> > link/ether 00:15:60:53:47:f5 brd ff:ff:ff:ff:ff:ff
> > inet 10.246.14.212/23 brd 10.246.15.255 scope global eth0
> > inet6 fe80::215:60ff:fe53:47f5/64 scope link
> > valid_lft forever preferred_lft forever
> > 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
> > link/ether 00:15:60:53:47:f4 brd ff:ff:ff:ff:ff:ff
> > 4: sit0: <NOARP> mtu 1480 qdisc noop
> > link/sit 0.0.0.0 brd 0.0.0.0
> > [root_at_localhost ~]#
>
> > status:
>
> > [oracle_at_localhost ~]$ lsnrctl status
>
> I would:
>
> - disable IP V6 on the interface you use, eth0
> - reroute the IPV6 traffic over eth1 (seems unused...)
> - stop the firewall and see what gives. If that
> is the cause, change the firewall to accept SQL*Net
> traffic, or reconfigure oracle to either use connection
> manager, or use multiple circuits (the former Multi Threaded
> Server option). Both allow for SQL*Net over one port (or a
> pre-defined range of ports), which allows the firewall
> to stay in place. It still needs adapting, of course!
>
> listener.ora would be handy
> --
> Regards,
> Frank van Bortel
>
> Top-posting is one way to shut me up...

Thank you for your kind help Frank. Luckily the problem is solved now... let's enjoy the sunday ;) Received on Sun Oct 28 2007 - 05:54:48 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US