Re: DBAs running root.sh

From: Hans Forbrich <fuzzy.graybeard_at_gmail.com>
Date: Mon, 03 Feb 2014 11:53:13 -0700
Message-ID: <52EFE599.4020306_at_gmail.com>



On 03/02/2014 10:08 AM, Austin Hackett wrote:
> How is this handled in your organisation? Have you ever been asked to have a centralised set of root.sh scripts under root control for this reason? Have you made it work?
Since I work with several organizations, I generally ask the SysAdmins to look at the root.sh and come up with their own solution.

For Clusterware and GI install, I prefer that they run it themselves, as ultimately they will lkely become responsible for the operations, and a lot of the processes run as root.

The script for DB is not difficult to follow, although there have been several changes in 12c. I still prefer them to run it, but when they realize the (11g and older) one just installs some things in /usr/local/bin, sets some ownership and permissions, and does a few setuid changes - WHICH THEY MUST BE AWARE OF IN ANY CASE - they tend to be more responsive to requests to run it. The 12c is a bit more intense, as it calls additional scripts, including in the network area so I may guide them through that. I find it helps when I keep them involved.

The root.sh in each ORACLE_HOME should be version controlled or at least backed up before upgrades in any case. I myself tend to back up the old one and do a diff before running it or asking for it to be run.

Centralized? Never tried, and don't really see it happening. Every upgrade can change it, and that means there could be differences between ORACLE_HOME/root.sh versions.

/Hans

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Feb 03 2014 - 19:53:13 CET

Original text of this message