Re: exadata role separation between gi and dbms
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: Freek.DHooge@xxxxxxxxx
- Date: Mon, 26 Mar 2012 15:08:47 +0100
Freek,
I've seen all sorts of systems, but I most definitely prefer those where *no
* oracle environment variables are set by default in the profile so that
oraenv or some other environment script has to be run before doing
anything.
I also would prefer to separate the clusterware user from the grid user,
because even if there isn't a formal separation of duties then at least
having to logon (or su) to some other account helps the grey matter notice
the context switch.
I rather like grid control, but have found that it really doesn't like
multiple software home owners unfortunately (12c not tested for this) and
you get a number of bugs or config steps as a result of the different uid
for files or scripts.
On Mon, Mar 26, 2012 at 2:44 PM, D'Hooge Freek <Freek.DHooge@xxxxxxxxx>wrote:
> Andy,
>
> Yes, I'm using multiple homes on non-exadata systems.
> But I normally use a different os user for each home and preset the env
> variables in the bash_profile instead of using oraenv. I have found this
> minimizes the chance on "oopses" where for instance a database is started
> under the wrong home.
>
> Kind regards,
>
> Freek D'Hooge
> Uptime
> Oracle Database Administrator
> email: freek.dhooge@xxxxxxxxx
> tel +32(0)3 451 23 82
> http://www.uptime.be
> disclaimer: www.uptime.be/disclaimer
>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of Andy Colvin
> Sent: maandag 26 maart 2012 14:52
> To: oracle-l
> Subject: Re: exadata role separation between gi and dbms
>
> How do you handle non-Exadata systems with multiple Oracle homes? oraenv
> is your friend. In most of the installations I've worked on, customers
> chose to go with everything under the oracle account, as it's easier to set
> your environment than remember to switch user accounts for every purpose.
> Andy Colvin
>
> Principal Consultant
> Enkitec
> andy.colvin@xxxxxxxxxxx
> http://blog.oracle-ninja.com
>
> On Mar 26, 2012, at 4:57 AM, D'Hooge Freek wrote:
>
> > Hi,
> >
> > I'm looking for some real world experiences with user separation setups
> on Exadata.
> >
> > The default on Exadata setups seems to be to install both the grid
> infrastructure software and the db software under the same user instead of
> using a separate grid user for the GI.
> >
> > On non Exadata RAC setups I normally use 2 separate users for this, but
> as this is my first Exadata I don't really know what would be the best
> thing to do.
> >
> > If it is really the default, I would be inclined to install everything
> under the oracle user, but then you have to remember to set or modify the
> environment variables each time you need to work on the asm or the db
> instance.
> >
> > So, if you have an Exadata setup, did you use a separate grid user or
> not and would you do the same if you had to start over again?
> > What are the benefits / drawbacks to use (or not use) different users?
> >
> >
> > Kind regards,
> >
> > Freek D'Hooge
> > Uptime
> > Oracle Database Administrator
> > email: freek.dhooge@xxxxxxxxx
> > tel +32(0)3 451 23 82
> > http://www.uptime.be
> > disclaimer: www.uptime.be/disclaimer
> >
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
//www.freelists.org/webpage/oracle-l
Other related posts:
