How to Clean Up a Failed Grid Infrastructure Installation
This article is about how to clean up a failed Grid Infrastructure installation. It specifically describes what do if the "root.sh" script fails during this process and want to start all over again.
On all cluster nodes except the last, run the following command as the "root" user.
# perl $GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force
On the last cluster node, run the following command as the "root" user.
# perl $GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force -lastnode
This final command will blank the OCR configuration and voting disk.
If above command doesn't work then please use
$/Grid_home/crs/install/rootcrs.sh -deconfig -force
Now "root.sh" can be rerun , but need to prepare ASM disks before doing so.
If /Grid_home/crs/install/rootcrs.sh -deconfig -force
Once you attempt an installation, your ASM disks are marked as being used, so they can no longer be used as candidate disks.
To revert them to candidate disk do the following.
Overwrite the header for the relevant partitions using the "dd" command.
# dd if=/dev/zero of=/dev/sdb1 bs=1024 count=100
Remove and create the ASM disk for each partition.
# /etc/init.d/oracleasm deletedisk CRS /dev/sdc1
# /etc/init.d/oracleasm createdisk CRS /dev/sdc1
The disks will now be available as candidate disks.
Log:
/usr/sbin/oracleasm createdisk CRSVOL ip-192.168.1.70:3260-iscsi-iqn.2006-01.com.openfiler:crsvol-lun-0-part1
dd if=/dev/zero of=/dev/oracleasm/disks/CRSVOL bs=1M count=10
[root@shsdbdr01 disks]# dd if=/dev/zero of=/dev/oracleasm/disks/CRSVOL bs=1M count=10
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 1.53923 s, 6.8 MB/s
For Reference Oracle Support Doc ID:
How to Deconfigure/Reconfigure(Rebuild OCR) or Deinstall Grid Infrastructure (Doc ID 1377349.1)
Comments
Post a Comment