Re: listener intermittently down

Vasu,

you are indeed on the right guess :(
yup this setting was put since development....

the setting was set up due to many port 6101 IDLE TIME when we checked through netstat -l | grep 6101 | wc -l

there are 6000 or even more. so I follow what metalink mention in the workaround.
also I set for the inbound_timeout parameter to 120, but again it didn't help.

hm....i'll find out the listener log as alex suggested....

regards
ujang

On Nov 11, 2007 11:00 PM, Vasu Balla <appsdba_at_gmail.com> wrote:
> Ujang,
>
> having read through the thread so far.. my wild guess is that the
> following setting in your listener.ora is making CRS to think that
> listner is down and it might be trying to start it
>
> SUBSCRIBE_FOR_NODE_DOWN_EVENT_LSNR_<SID> = OFF
>
> > The next thing you are mentioning: multiple lines with listener
> > -inherit. That would indicate the cluster daemon trying to start the
> > listener, because it thinks the listener is down. (provided you are
> > the only one on the system, and not a colleague trying to start the
> > listener because he found the listener to be not functioning too, just
> > like you)
> > Evidence of this event will be in the cluster log file.
>
>
> > > > > have been set on listerner.ora
> > > > > SUBSCRIBE_FOR_NODE_DOWN_EVENT_LSNR_HQRAC1=OFF
> > > > > INBOUND_CONNECT_TIMEOUT_LSNR_HQRAC1 = 120
>

--
http://www.freelists.org/webpage/oracle-l