How to Proceed from Failed 11gR2 Grid Infrastructure (CRS) Installation [ID 942166.1] | |||||
修改时间 21-SEP-2011 类型 BULLETIN 状态 PUBLISHED |
In this Document
Purpose
Scope and Application
How to Proceed from Failed 11gR2 Grid Infrastructure (CRS) Installation
Deconfigure and Reconfigure of Standalone Server (Oracle Restart):
Deinstall of Grid Infrastructure Standalone Server:
Deconfigure and Reconfigure of Grid Infrastructure Cluster:
Deinstall of Grid Infrastructure Cluster:
Complete Configuration Assistant if OUI is Closed:
References
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 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/root.sh"
As grid user, execute $GRID_HOME/deinstall/deinstall
Identify cause of root.sh failure by reviewing logs in $GRID_HOME/cfgtoollogs/crsconfig and$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, 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 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.
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.
相关内容
产品
|