Oracle root.sh

[SAM_24]

Hi,

Our company is very big and we have 100s of database. Each day some upgrade and new installation will be there. Oracle DBA will request me to run root.sh script. Is there any workaround Can I do so root.sh can be ran as oracle user?

Thanks.

[T G Manikandan]

root.sh script is neccessry for to finish the installation of oracle.

If copies some files into the /usr/bin directory and it makes entry in the oratab file.

The root.sh should be run only by root.

Oracle requires this to be run only for the first time during the oracle installation.

Thanks

[Stefan Farrelly]

We experimented with a setuid to root C program an a script but we had problems with both - running a setuid to root program is just not the same as being logged in as root and running it so we had to temporarily let our DB's have root access (but with shell history loggin on so we could check what they were doing).

[harry d brown jr]

sudo??

su??

And does it really matter if you give your DBA root access on a machine that is being BUILT - and apparently DOESN'T have production on it yet??

live free or die
harry

[Wodisch]

Hi,

if you read today's "root.sh" scripts, then you can see that what they do is not that difficult/dangerous, so that you could easily even do that yourself (you beeing the true "root"), even BEFORE the oracle installation starts. Then there would be no need for your DBAs to even run the script at all...

Just my $0.02,
Wodisch

[Sebastien Masson]

I run into same problem, and I try first giving sudo to the root.sh command. Bad idea, DBA use this power to change other think in the system by modifying root.sh script before run it. Until bad variable initalization and a rm -rf /$badvar append. After recoer the sysmte, I kill all of them.

Now DBAs do updagre on sandbox (dev machine) and then I sync the Oracle stuff on the production side. Depend on your DBA confort that may be a solution. If you have a paranoid DBA, then that may be a pain in the ass each time.

No miracle solution to that.