Re: Listener in Oracle 8.1.7

1. With 8i remote_password_login (I'm too lazy to look it up ... you'll what I mean when you open init.ora) is set to exclusive by default - this is not the case prior to 8i. Set it to NONE if you don't to give a password when connection as internal ! This is normal behavious. To change the password recreate the password file using orapwd
2. This is because you have a service defined in listener.ora AND, starting from Oracle 8i PMON will register itself with the listener - hence you'll have 2 services for one DB. It has nothing to do with you connecting as internal with servermanager - merely a coincidence... Actually with 8i you don't even need a listener.ora anymore - but this is only recommended for reaaaal simple setups. If you don't whant PMON to register itself with the listener you can set an event (I don't know the event number by hear - if anyone is interested I'll look it up) OR you can do it lazy dba style :-) by setting local_listener in init.ora to a non-existing listener... this way PMON will fail to register at startup and won't try again !

regards,
Koert

"Sybrand Bakker" <oradba_at_sybrandb.demon.nl> wrote in message news:3lfqvt42m2j5tejilr638pa1bud6dt8cbi_at_4ax.com...
> On Thu, 22 Nov 2001 17:02:10 +0100, "Hans-Peter"
> <hans-peter.henrichsen_at_capgemini.se> wrote:
>
> >Hello,
> >
> >I have two questions..
> >
> >IZve installed Oracle 8.1.7 on our Windows 2000 server. I realized when I
> >try to connect internal in Server manager I have to confirm with
password.
> >As far as I know you should be able to connect internal without
confirming
> >with password. Right? if so, how?
> >
> >When I run "lsnrctl status" I see that I have one service of my Instance
> >(PDEV). Then I connect internal in Server manager and run lsnrctl status
> >again. Now there is two service of my Instance. Should it be like this?
> >
> >If somebody has an answer, please contact me!
> >
> >Kind Regards,
> >Hans-Peter Henrichsen
> >hans-peter.henrichsen_at_capgemini.se
> >
> >
>
> 1 Looks like an incorrect install. The ora_<sid>_dba local group or
> ora_dba local group is created in normal cases. This takes care of
> connect / as sysdba in normal cases (please stop using internal, it is
> obsolete for many releases and it has disappeared completely from 9i)
> However if you are connected to the server as domain administrator,
> the group won't be created.
> Right now you probably should create the local group manually instead
> of re-installing everything
>
> 2 You probably have the multithreaded server configured, and that is
> only guess work as you don't post the listener status about, but only
> describe it in vague terms.
> Whether you need to use MTS at all depends on the number of users that
> are going to be connected,
>
> Hth
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Thu Nov 22 2001 - 15:07:36 CST