Re: Listener starts but can't stop it.... ??????

"Dominic Baines" <dombaines_at_mmbq.demon.co.uk> wrote in message news:<8wrE7.45$Cl3.53671_at_news6-win.server.ntlworld.com>...
> Have recovered from a system crash and recovered the whole of a live
> database, install etc...
>
> DB seems fine (acts fine anyway) and dbstart and dbshut operate as before.
>
> lsnrctl start starts the listener as you'd expect but....
> lsnrctl stop can't stop the listeners... it's complaining about a password.
>
> Anyone shed any light on this behaviour ?
>
> I can run kill-9 <pid> so the listener stops and I stop the DB first.
>
> It's RedHat 7.1 (with binutils downgraded, and the i386 lib files copied
> etc...) and Oracle 8.1.7..
>
> Dev box so non-critical but would be interesting to know what is going on.

Dominic, since at least sqlnet version 1.1 you have always had to set the password (at least if it was set) before issuing the stop command.  You should check your listerner.ora file and see what you have PASSWORDS_LISTENER= set to then:

lsnrctl
set password oracle
stop

If you are sure you never had to do this before then you should verify that 1- the same listener file is in use and 2- someone did not change it

• Mark D Powell --