RE: LSNRCTL Password

of list ORACLE-L > Subject: RE: LSNRCTL Password > > Downside only if you want to have listener on different box - maybe for > load > balancing. > > Alex Hillman > > -Original Message- > Sent: Thursday, May 10, 2001 7:01 PM > To: [EMAIL PROTECTED]; Hillman, A

Re: LSNRCTL Password

Neat trick., hadn't thought of that. Any downsides to using localhost? Jared On Thursday 10 May 2001 14:52, Hillman, Alex wrote: > This is why I now use localhost instead of hostname. > > Alex Hillman > > -Original Message- > Sent: Thursday, May 10, 2001 4:26 PM > To: Multiple recipie

RE: LSNRCTL Password

Downside only if you want to have listener on different box - maybe for load balancing. Alex Hillman -Original Message- Sent: Thursday, May 10, 2001 7:01 PM To: [EMAIL PROTECTED]; Hillman, Alex Neat trick., hadn't thought of that. Any downsides to using localhost? Jared On Thursda

RE: LSNRCTL Password

This is why I now use localhost instead of hostname. Alex Hillman -Original Message- Sent: Thursday, May 10, 2001 4:26 PM To: Multiple recipients of list ORACLE-L Alex, >Could you explain please how somebody with DBA provileges on >another node >can shutdown listener on another node

RE: LSNRCTL Password

t;>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 5/10/01, 3:25:30 PM, John Kanagaraj <[EMAIL PROTECTED]> wrote regarding RE: LSNRCTL Password: > Alex, > >Could you explain please how somebody with DBA pr

RE: LSNRCTL Password

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 confi

RE: LSNRCTL Password

Yea, SAs disable all security threats. Sure Uh-huh Fine Whatever || -Original Message- || From: Hillman, Alex [mailto:[EMAIL PROTECTED]] || Sent: Thursday, May 10, 2001 1:23 PM || To: Multiple recipients of list ORACLE-L || Subject: RE: LSNRCTL Password || || || But usually all

RE: LSNRCTL Password

EMAIL PROTECTED]] || Sent: Thursday, May 10, 2001 11:42 AM || To: Multiple recipients of list ORACLE-L || Subject: RE: LSNRCTL Password || || || Could you explain please how somebody with DBA provileges on || another node || can shutdown listener on another node without logging as || user of the

RE: LSNRCTL Password

rsh, I'd guess. || -Original Message- || From: Hillman, Alex [mailto:[EMAIL PROTECTED]] || Sent: Thursday, May 10, 2001 11:42 AM || To: Multiple recipients of list ORACLE-L || Subject: RE: LSNRCTL Password || || || Could you explain please how somebody with DBA provileg

RE: LSNRCTL Password

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. Akex Hillman -Original Message- Sent: Wednesday, May 09, 2001 9:50 PM To: Multiple recipients of list ORACLE-L

Re: LSNRCTL Password

I see someone has already given you instructions on how to use a password with listener.ora. Just thought I might add that they are fairly useless, as you *cannot* prevent someone with dba group privileges on another node of the network from shutting down your listener. They won't be able to st

RE: LSNRCTL Password

If password protection is being used, you must set the password before you can issue the STOP command. When using passwords for the listener, you cannot issue the STOP command at the operating system level because the password can only be set within the lsnctrl utility. There are two types of p