Root.sh Fails when Installing Oracle 10g CRS
Hi All,
There are many reasons for the failing for root.sh when you are installing Oracle 10gR2 CRS. I have observed some of them and listed below.
CAse 1 :
Root.sh fails when run on the last node of the RAC on any platform saying that
The given interface(s), “eth0″ is not public. Public interfaces should be used to configure virtual IPs.
This issue is specific to Oracle 10.2.0.1 only (noted in BUG 4437727) and needs to be resolved before continuing. The easiest workaround is to re-run vipca (GUI) manually as root from the last node in which the error occurred. Please keep in mind that vipca is a GUI and will need to set your DISPLAY variable accordingly to your X server:
# $ORACLE_HOME/bin/vipca
Go back to the OUI and acknowledge the “Execute Configuration scripts” dialog window.
CASE 2:
In case of Solaris when the RAW device is used for configuring OCR and when cylinder 0 or first 1 MB of the partition is not skipped ( Refer my previous article for more details)
In that case root.sh fails on the first node itself and gives the following error
Failed To Upgrade Oracle Cluster Registry Configuration
In that case cleanup the failed CRS installation, Recreate the partition for OCR and Voting Disk by skipping the first few cylinders using format command and reinstall CRS
CASE 3:
When Different partition names are used to identify the OCR/Voting partitions RAW partitions from different Nodes for e.g
From Node 1 location of OCR is identified as
/dev/rdsk/c3t40d0s0
From Node 2 same location of OCR is identified as
/dev/rdsk/c3t44d0s0
In the above case use symbolic links so that OCR location is identified using same name from both the location
CASE 4:
If your hostname of the nodes contains a mixture of small case letters and Capital alphabets for e.g WiMAXDB, WiMAXDB
Using such hostnames may not be supported by Oracle 10g CRS.you can identify such case by going into $ORA_CRS_HOME/log and if there are 2 directory created with different names like in my case it was the following directories were found in $ORA_CRS_HOME/log directory
WiMAXDB1 and wimaxdb1
In that case cleanup the failed CRS installation,change the hostname and then reinstall CRS.
CASE 5:
Finally the root.sh script can also fail due to improper permissions to CRS home in UNIX systems. during CRS installation the CRS home should be owned by oracle user and when you run root.sh script you will see several warnings as shown
WARNING: ‘/oracle’ not owned by root
WARNING:’/oracle/clusterware’ not owned by root
WARNING:’/oracle/clusterware/crs’ not owned by root
WARNING:’/oracle/clusterware/crs/oracle’ not owned by root
WARNING:’/oracle/clusterware/crs/oracle/10.2.0′ not owned by root
However only when the CRS is completely and sucessfully installed you can change the ownership to the root user of CRS home
chown -R root:oinstall /oracle/clusterware/crs/oracle/product/10.2.0
chmod -R 775 /oracle/clusterware/crs/oracle/product/10.2.0