Re: 1 oracle user per server or 1 per database
Date: Mon, 1 Feb 2010 14:47:50 -0300
I've seen all combinations, all with pro's and con's.
1 user per database:
* no need to run oraenv * required one home for database * requires more complex scripting for automating database operations (cronedbackups or stats gathering, etc)
1 user per release:
* reduces the number of homes and keeps everything elegant. This is my favorite option.
* requires use of oraenv.
1 user per server:
* reduces the number of homes
* you can't tell from ps -ef |grep pmon in which release a DB is, you need to check /etc/dbora
I'm sure there are many more points to consider... this is just a list from the top of my head.
On Mon, Feb 1, 2010 at 10:54 AM, D'Hooge Freek <Freek.DHooge_at_uptime.be>wrote:
> I'm searching for arguments pro and con the use of a dedicated (os) oracle
> user per database versus a single oracle user per server.
> The os platform is Linux. The database versions will probably be a mix of
> 10gR2 and 11gR2.
> Is anyone using the new 11gR2 grid infrastructure with multiple oracle
> users for the databases? Any known pitfalls with this?
> Freek D'Hooge
> Oracle Database Administrator
> email: freek.dhooge_at_uptime.be
> tel +32(0)3 451 23 82
> disclaimer: www.uptime.be/disclaimer