【RAC】How to Proceed from Failed 11gR2 CRS Installation

Applies to:  [ID 942166.1]

Oracle Server – Enterprise Edition – Version: 11.2.0.1 to 11.2.0.2 – Release: 11.2 to 11.2
Generic UNIX   Generic Linux

Goal

This goal of this note is to provide 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

Solution

Deconfigure and Reconfigure of Standalone Server (Oracle Restart):

To deconfigure:

As root, execute “$GRID_HOME/crs/install/roothas.pl -deconfig -force -verbose”

If it fails, please disable CRS, 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”

Deinstall of Grid Infrastructure Standalone Server:

As grid user, execute $GRID_HOME/deinstall/deinstall

Deconfigure and Reconfigure of Grid Infrastructure Cluster:

Identify cause of root.sh failure by reviewing logs in $GRID_HOME/cfgtoollogs/crsconfigand $GRID_HOME/log, once cause is identified, deconfigure and reconfigure with steps below – please 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 fixed, root.sh can be executed again on the failed node, if it succeeds, you can continue with the installation, 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 and VD disk also.

Note:

A. Step1 and 2 can be skipped on node(s) where root.sh haven’t been execute.

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 

$ rm -rf $GRID_HOME/gpnp/*
$ mkdir -p $GRID_HOME/gpnp/profiles/peer $GRID_HOME/gpnp/wallets/peer$GRID_HOME/gpnp/wallets/prdr $GRID_HOME/gpnp/wallets/pa$GRID_HOME/gpnp/wallets/root

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.

Step 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.

Deinstall of Grid Infrastructure Cluster:

Case 1: “root.sh” never ran on this cluster, then as grid user, execute $GRID_HOME/deinstall/deinstall

Case 2: “root.sh” already ran, then follow the step below – please keep in mind that you will need wait till each step finishes successfully before move to next one:

Step 1: As root, run “$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force” on all node, 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 and VD disk also.

Step 3: As grid user, run “$GRID_HOME/deinstall/deinstall” on any node.

Complete Configuration Assistant if OUI is Closed:

If  $GRID_HOME/cfgtoollogs/configToolAllCommands doesn’t exist, create a shell script. with the following content:

If any configuration assistants already finished successfully previously and you’d like to skip them, please be sure to set RERUN to false, for example:

As grid user, execute $GRID_HOME/cfgtoollogs/configToolAllCommands on first node.