Thanks Sybrand - I knew you would look that up for me - did you also find
that event I was talking about ?
> > Actually with 8i you don't even need a listener.ora anymore - but this
is
> > only recommended for reaaaal simple
> > setups.
> is simply incorrect.
> You do need the listener.ora to setup for external procedure calls and you
> do need the listener.ora for OEM.
yep - the OEM tcl scripts parse that stuff and yep you'll need a
listener.ora for external procedure calls - also you want to
configure anything exotic like queuesize or SDU/TDU stuff you'll need
listener.ora... but for simply
connecting to the DB you don't need it - it think its a pretty useless
feature too ... but hey - if you think it's not correct .. try it
yourself ....
you know what - since you like metalink that much I looked it up for you :
doc.id 76636.1
I might be very lazy - but I know it - and I admit it :-) I only have a good
idea now and then that enables me to do
even less work ... aren't 99% of all DBA's like this ? why else create a
website www.lazydba.com :-)
PURPOSE
The purpose of this document is to discuss the Service Registration feature
of Net8i.
SCOPE & APPLICATION
This document is intended for DBAs.
RELATED DOCUMENTS
Note 76531.1 : Service Name Usage in Net8i
1.0 INTRODUCTION
Prior to Oracle 8i, a listener was statically configured (listener.ora) to
service a given set of SIDs. From 8i, PMON dynamically registers a database
service with the listener.
Further, if the listener is running on the default TCP port of 1521, then
there is no need to configure a listener.ora at all.
2.0 USING A DEFAULT LISTENER
A listener.ora file is not required in order to use the default listener.
The listener is started in the conventional manner:
$lsnrctl start
This listener will listen on two addresses:
(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
(ADDRESS=(PROTOCOL=tcp)(PORT=1521))
In order to change parameters to non default values (such as enabling
listener tracing), then a listener.ora should be created with the relevant
parameters specified. The listener then needs to be restarted.
By default, PMON will register the database service with the listener on
port
1521.
... blah blah
"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
news:tvqu82ij8ohbcd_at_corp.supernews.com...
> Next time, please look up look up the documentation when you are not
certain
> of your answer, instead of being lazy.
>
> From the 8.1.7 documentation
>
> REMOTE_LOGIN_PASSWORDFILE
> Parameter type: String
>
> Syntax: REMOTE_LOGIN_PASSWORDFILE=
>
> {NONE | SHARED | EXCLUSIVE}
>
> Parameter class: Static
>
> Default value: NONE
>
> Oracle Parallel Server: Multiple instances must have the same value.
>
> REMOTE_LOGIN_PASSWORDFILE specifies whether Oracle checks for a password
> file and how many databases can use the password file.
>
> NONE: Oracle ignores any password file. Therefore, privileged users must
be
> authenticated by the operating system.
>
> EXCLUSIVE: The password file can be used by only one database and the
> password file can contain names other than SYS and INTERNAL. This setting
is
> required for Oracle Parallel Server.
>
> SHARED: More than one database can use a password file. However, the only
> users recognized by the password file are SYS and INTERNAL.
>
>
> Hence, your answer is simply incorrect.
>
>
> Also this remark
>
> > Actually with 8i you don't even need a listener.ora anymore - but this
is
> > only recommended for reaaaal simple
> > setups.
>
> is simply incorrect.
> You do need the listener.ora to setup for external procedure calls and you
> do need the listener.ora for OEM.
>
>
> Regards
>
>
> --
> Sybrand Bakker
> Senior Oracle DBA
>
> to reply remove '-verwijderdit' from my e-mail address
>
>
>
>
> "koert54" <koert54_at_nospam.com> wrote in message
> news:sOdL7.5396$7r1.1570393273_at_hestia.telenet-ops.be...
> >
> > 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 - 16:32:21 CST
