Purpose
This note provides steps to proceed from failed 11gR2 Grid Infrastructure installation. Similar procedure for 10gR1, 10gR2 or 11gR1 available in note 239998.1 and note 399482.1
If upgrade to 11.2 GI fails, refer to note 969254.1 for details. If 11.2 GI has been up and running and need to be deconfigured/deinstalled/reconfigured/reinstalled, refer to note 1377349.1 and note 1354258.1 
Scope
This document is intended for Oracle Clusterware/Oracle RAC Database Administrators and Oracle support engineers. 
Details
#################################################
A. OUI Failure
Case applies here is when runInstaller fails before user is prompted to execute rootupgrade.sh.
Refer to note 1056322.1 for solution details.
#################################################
B. GI Standalone Deconfigure and Reconfigure (Oracle Restart)
To deconfigure:
As root, execute “$GRID_HOME/crs/install/roothas.pl -deconfig -force -verbose”
If it fails, please disable GI, reboot the node and try the same command:
As root, execute “$GRID_HOME/bin/crsctl disable has”
As root, reboot the node; once the node comes backup, execute above deconfigure command again.
To reconfigure:
As root, execute “$GRID_HOME/root.sh”
#################################################
C. GI Cluster Deconfigure and Reconfigure
Identify cause of root.sh failure by reviewing logs in $GRID_HOME/cfgtoollogs/crsconfig and $GRID_HOME/log, once cause is identified and problem is fixed, deconfigure and reconfigure with steps below – keep in mind that you will need wait till each step finishes successfully before move to next one:
Step 0: For 11.2.0.2 and above, root.sh is restartable.
Once cause is identified and the problem is fixed, root.sh can be executed again on the failed node. If it succeeds, continue with your planned installation procedure; otherwise as root sequentially execute “$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force” and $GRID_HOME/root.sh on local node, if it succeeds, continue with your planned installation procedure, otherwise proceed to next step (Step 1) of the note.
Step 1: As root, run “$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force” on all nodes, except the last one.
Step 2: As root, run “$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force -lastnode” on last node. This command will zero out OCR, Voting Disk and the ASM diskgroup for OCR and Voting Disk
———————————————-
Note:
a. Step1 and 2 can be skipped on node(s) where root.sh haven’t been executed this time.
b. Step1 and 2 should remove checkpoint file. To verify:
ls -l $ORACLE_BASE/Clusterware/ckptGridHA_.xml
If it’s still there, please remove it manually with “rm” command on all nodes
c. If GPNP profile is different between nodes/setup, clean it up on all nodes as grid user
$ find <GRID_HOME>/gpnp/* -type f -exec rm -rf {} \;          
The profile needs to be cleaned up:
c1. If root.sh is executed concurrently – one should not execute root.sh on any other nodes before it finishes on first node.
c2. If network info, location of OCR or Voting Disk etc changed after Grid is installed – rare
———————————————-
tep 3: As root, run $GRID_HOME/root.sh on first node
Step 4: As root, run $GRID_HOME/root.sh on all other node(s), except last one.
Step 5: As root, run $GRID_HOME/root.sh on last node.
#################################################
D. Grid Infrastructure Deinstall
As grid user, execute “$GRID_HOME/deinstall/deinstall” and follow the instructions, for details, refer to the following documentation for your platform:
Oracle Grid Infrastructure Installation Guide
How to Modify or Deinstall Oracle Grid Infrastructure
If there’s any error, deconfig the failed GI with steps in Section B or C, and deinstall manually with note 1364419.1 
#################################################
E. OUI Plug-in Failure or OUI Window Closed While Running root.sh
Case applies here is OUI plug-in failure after root.sh has been executed successfully on all nodes or OUI window closed while running root.sh
Identify the cause of failed plug-in. Once root cause is identified and the issue is resolved, refer to note 1360798.1

PS: This article comes from MOS…

《Oracle 10g&11.1 Clusterware (CRS)安装失败如何卸载》请参考How to Proceed From a Failed 10g or 11.1 Oracle Clusterware(CRS)Installation

这篇文章[239998.1]可以帮助DBA分析和理解如何将安装失败的10g和11.1版本的CRS成功卸载，该篇文章适用于清除安装失败的10.1.0.2 to 11.1.0.7版本的CRS，对于清除安装失败11.2版本的CRS请参考文档[942166.1 How to Proceed from Failed 11gR2 Grid Infrastructure (CRS) Installation]

Not cleaning up a failed CRS install can cause problems like node reboots. Follow these steps to clean up a failed CRS install:
1. Run the rootdelete.sh script then the rootdeinstall.sh script from the $ORA_CRS_HOME/install directory on any nodes you are removing CRS from. Running these scripts should be sufficent to clean up your CRS install. Rootdelete.sh accepts options like nosharedvar/sharedvar, and nosharedhome/sharedhome. Make yourself familiar with these options by reading the Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide. If you have any problems with these scripts please open a service request.

If for some reason you have to manually remove the install due to problems with the scripts, continue to step 2:
2. Stop the Nodeapps on all nodes:
srvctl stop nodeapps -n
3. Prevent CRS from starting when the node boots. To do this issue the following as root:
Sun:

rm /etc/init.d/init.cssd 
rm /etc/init.d/init.crs 
rm /etc/init.d/init.crsd 
rm /etc/init.d/init.evmd 
rm /etc/rc3.d/K96init.crs 
rm /etc/rc3.d/S96init.crs 
rm -Rf /var/opt/oracle/scls_scr 
rm -Rf /var/opt/oracle/oprocd 
rm /etc/inittab.crs 
cp /etc/inittab.orig /etc/inittab 

Linux:

rm /etc/oracle/* 
rm -f /etc/init.d/init.cssd 
rm -f /etc/init.d/init.crs 
rm -f /etc/init.d/init.crsd 
rm -f /etc/init.d/init.evmd 
rm -f /etc/rc2.d/K96init.crs 
rm -f /etc/rc2.d/S96init.crs 
rm -f /etc/rc3.d/K96init.crs 
rm -f /etc/rc3.d/S96init.crs 
rm -f /etc/rc5.d/K96init.crs 
rm -f /etc/rc5.d/S96init.crs 
rm -Rf /etc/oracle/scls_scr 
rm -f /etc/inittab.crs 
cp /etc/inittab.orig /etc/inittab

HP-UX:

rm /sbin/init.d/init.cssd 
rm /sbin/init.d/init.crs 
rm /sbin/init.d/init.crsd 
rm /sbin/init.d/init.evmd 
rm /sbin/rc2.d/K960init.crs 
rm /sbin/rc2.d/K001init.crs 
rm /sbin/rc3.d/K960init.crs 
rm /sbin/rc3.d/S960init.crs 
rm -Rf /var/opt/oracle/scls_scr 
rm -Rf /var/opt/oracle/oprocd 
rm /etc/inittab.crs 
cp /etc/inittab.orig /etc/inittab

HP Tru64:

rm /sbin/init.d/init.cssd 
rm /sbin/init.d/init.crs 
rm /sbin/init.d/init.crsd 
rm /sbin/init.d/init.evmd 
rm /sbin/rc3.d/K96init.crs 
rm /sbin/rc3.d/S96init.crs 
rm -Rf /var/opt/oracle/scls_scr 
rm -Rf /var/opt/oracle/oprocd 
rm /etc/inittab.crs 
cp /etc/inittab.orig /etc/inittab 

IBM AIX:

rm /etc/init.crs 
rm /etc/init.crsd 
rm /etc/init.evmd 
rm /etc/rc.d/rc2.d/K96init.crs 
rm /etc/rc.d/rc2.d/S96init.crs 
rm -Rf /etc/oracle/scls_scr 
rm -Rf /etc/oracle/oprocd 
rm /etc/inittab.crs 
cp /etc/inittab.orig /etc/inittab

4. If they are not already down, kill off EVM, CRS, and CSS processes or reboot the node:

ps -ef | grep crs
kill -9 procid
ps -ef | grep evm
kill -9 procid
ps -ef | grep css
kill -9 procid

Do not kill any OS processes, for example icssvr_daemon process !
5. If there is no other Oracle software running (like listeners, DB’s, etc…), you can remove the files in /var/tmp/.oracle or /tmp/.oracle. Example:

rm -f /var/tmp/.oracle/* 或者 rm -f /tmp/.oracle/*

6. Remove the ocr.loc, usually the ocr.loc can be found at /etc/oracle
7. De-install the CRS home in the Oracle Universal Installer
8. Remove the CRS install location.
9. Clean out the OCR and Voting Files with dd commands. Example:

dd if=/dev/zero of=/dev/rdsk/V1064_vote_01_20m.dbf bs=1M count=256
dd if=/dev/zero of=/dev/rdsk/ocrV1064_100m.ora bs=1M count=256

See the Clusterware Installation Guide for sizing requirements…
If you placed the OCR and voting disk on a shared filesystem, remove them.
If you are removing the RDBMS installation, also clean out any ASM disks if they have already been used.
10. The /tmp/CVU* dir should be cleaned also to avoid the cluvfy misreporting.
11. It is good practice to reboot the node before starting the next install.
12. If you would like to re-install CRS, follow the steps in the Oracle Clusterware Installation manual.

PS: This article comes from MOS…