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