Of course, in the bad old days, they told us to use "oradba" ... you might still that here and there. r, Gus On Sun, Oct 17, 2010 at 1:34 PM, Alex List <alex@xxxxxxxxxxxxxx> wrote: > Hi Rodd and William, > > Thanks a lot for the explanation, I was in doubt if it was true, but now I > am relaxed that sometimes in my installations I had to change names. > > Thanks again. > Alex > > > > > On Sun, Oct 17, 2010 at 14:19, Rodd Holman <rodd.holman@xxxxxxxxx> wrote: > >> The "oracle" user by default has no more or less privileges than joe, bob, >> or john. It's just a userid created by your SA to manage oracle software >> installs and running the database. The extra privileges are granted to the >> user by assigning groups, or adjusting kernel and processing limits as >> described in the oracle installation documentation for unix systems. You >> could name the user anything you want to, but why would you? Most of the >> folks in this world, and Oracle's own documentation use the "oracle" user >> for this purpose. This is one where most folks just go with the flow. >> >> --Rodd Holman >> >> On Fri, Oct 15, 2010 at 8:10 PM, William Muriithi < >> william.muriithi@xxxxxxxxxxxxxxxxxxx> wrote: >> >>> >>> This misconception may have come up because too many oracle documentation >>> advice the use of oracle as best practice. Someone may then have inferred >>> that to mean, it has special treatment by the OS and a myth was born >>> >>> ------------------------------ >>> ... >>> Its when we create an unix user account, the "oracle" user account >>> (spelled like this) has some extra advantages (like priorities and >>> privileges) on the operating system instead of creating something like >>> "oradb", "ora10g" or whatever we create. >>> >>> Looking for this info on the Internet, I didnt find, but if we consider >>> installing on Oracle Enterprise Linux perhaps might be truth!! ... just >>> guessing! >>> ... >>> >>> Alex >>> >>> >> >