Alex,
>Could you explain please how somebody with DBA provileges on
>another node
>can shutdown listener on another node without logging as user
>of the node
>where listener is running.
I fully agree with Jared. We encountered this when I duplicated the Prod
server (including the SQL*net config file) onto a Test box and bounced the
test box. The listener.ora file contains the name of the Prod server and the
automatic stop/start script executed a 'lsnrctl stop' as part of shutdown -
this sent a STOP signal to the identified host (the Prod server). This
stopped the listener on another system!!
It is quite easy to test this out - you can create a dummy listener.ora on
the Prod box, point that to the Dev box and stop the listener from Prod...
Hth,
John Kanagaraj
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: John Kanagaraj
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
