RE: Oracle instance startup user on Unix

Disagree with the   "There should be one listener process
per server.  Period.  "   We have multiple oracle/servers running on the
same UNIX server.  If all of them are running on one listener, then I
have to drop the listener for all if I need to shutdown SQL*NET access
to one.

Each database has it's own listener running on a different port...PLUS
we have one listener running for all databases that is on a NATTED IP
for administrative access through a VPN.

And none of them are on default 1521

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mercadante, Thomas F
(LABOR)
Sent: Wednesday, July 13, 2005 7:46 AM
To: rob.langmuir@xxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle instance startup user on Unix

Bob,

My concerns are management and security.

Let's tackle the easy one first:

Security.
Who will have access to the unix account where the database resides?
I'm assuming you have a DBA group.  Will you have exclusive access to
this unix account?  If everybody and his brother has the password for
this account, then the security of the database is non-existant.  You
will have no control over who can update anything.

Management.

Who is managing the server?  And who is managing Oracle on that server?
Zhu Chao makes a reasonable point about multiple Oracle homes and
accounts for different database instances.  But I would argue that
having them all in an Oracle unix account is much easier to manage.  

And finally the listener issue.  There should be one listener process
per server.  Period.  They should not be managing their own listener.
Just plain dumb.

My little 2 cents.

Tom

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of RSL
Sent: Wednesday, July 13, 2005 1:27 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Oracle instance startup user on Unix

We have a third-party application, which as part of installation
process,
uses it's own Unix account to create/startup Oracle database/instance.
They
also want to start a listener with this account.

In the future we plan to add our own instances/databases, and these will
all
be started/created using Oracle account.


I don't much like the idea of having two separate unix accounts involved
in
creating database(s) and starting instances.

Although there is no practical reason why this can't be done, can you
please
offer any reasons why you wouldn't /shouldn't do this.

Thanks..../Bob

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l

Other related posts: