In this Document
Goal
Solution
References
During the CRS clusterware installation, it is requested to run the $CRS_HOME/root.sh script on all nodes of the clusterware. The goal of this note is to provide a quick guide on how to debug/rerun the root.sh in order to solve any issue related to it.
This note applies to a CRS 10.2 and CRS 11.1 installation. For a CRS 10.1 installation, please use note:240001.1.
How to debug/rerun the root.sh during the CRS clusterware installation
If you are running root.sh the first time, please skip to step#6; otherwise, continue with step#1.
1. Shutdown the Oracle Clusterware stack on all the nodes using command "crsctl stop crs" as root user.
2. Backup the entire Oracle Clusterware home.
3. Execute <CRS_HOME>/install/rootdelete.sh on all nodes
USAGE: rootdelete.sh [local|remote] [sharedvar|nosharedvar] [shardhome|nosharedhome]
* local/remote: Use 'local', if it is run on local node. Default: local
* nosharedvar/sharedvar: Use 'sharedvar', if directory path of ocr.loc is shared across cluster nodes.Default: nosharedvar
* sharedhome/nosharedhome: Use 'sharedhome', if CRS home is shared across cluster nodes. Default: sharedhome
The rootdelete.sh will remove the init* scripts and the inittab entries. It will also remove the init* flag files.
4. Execute <CRS_HOME>/install/rootdeinstall.sh on the installing node
This script will wipe out OCR device used for Oracle Cluster Ready Services.
5. The following commands should return nothing:
* ps -e | grep -i 'ocs[s]d'
* ps -e | grep -i 'cr[s]d.bin'
* ps -e | grep -i 'ev[m]d.bin'
Eventually kill those processes or reboot the node.
6. Remove all files from /tmp/.oracle and /var/tmp/.oracle
7. edit the root.sh and add 'sh -x' before the two commands executed by it, e.g.
#!/bin/sh
sh -x /u01/app/oracle/product/crs102/install/rootinstall
sh -x /u01/app/oracle/product/crs102/install/rootconfig
8. collect the output via, e.g.
script /tmp/rootsh-node1.log
./root.sh
exit
9. Please send the rootsh-node1.log to Oracle Support for analyzing.
- In some cases, these messages can be found in the rootsh-<node_name>.log file: