Re: why did the listener stop??

These are probably silly questions but...

    Did the sysadmins reboot the server for any reason - quick patch, freeing a stuck process etc?

    Could anyone have run a shell script that includes a line to stop the listener?

"Howard J. Rogers" <dba_at_hjrdba.com> wrote in message news:3c198704$0$7496$afc38c87_at_news.optusnet.com.au...
> The obvious question is going to be: what does your listener log say?
>
> Regards
> HJR
> --
> ----------------------------------------------
> Resources for Oracle: http://www.hjrdba.com
> ===============================
>
> "fake" <fake_at_tamu.edu> wrote in message news:3C191A06.926F8A3C_at_tamu.edu...
> > Hi,
> >
> > Platform Info: Oracle 8.1.7 on SunOS 5.8 Generic_108528-10 sun4u sparc
> > SUNW,Ultra-250.
> >
> > Our listener.log shows the following info:
> > ==================
> > 13-DEC-2001 11:40:07 *
> > (CONNECT_DATA=(CID=(PROGRAM=)(HOST=server)(USER=oracle)
> > )(COMMAND=stop)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=134238208)) *
> > stop * 0
> > No longer listening on:
> > (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=server.tamu.edu)(PORT=1521)))
> > ===================
> >
> > I want to know what might cause the listener to stop? I know 'lsnrctl
> > stop listener' can do it. But is it the only way? I have asked around
> > and seems nobody did anything with the listener around that time.
> >
> > Any ideas?
> >
> > Bing
> >
> > Bing
> >
>
>
Received on Sun Dec 16 2001 - 09:18:59 CST