参考:
First, I'll remove the bad node from the cluster. I start by removing the RDBMS software from the good node's inventory.
[oracle@host01]$ ./runInstaller -updateNodeList ORACLE_HOME=$RDBMS_HOME "CLUSTER_NODES={host01}"
LOCAL_NODE=host01
Then I remove the GI software from the inventory.
$ ./runInstaller -updateNodeList ORACLE_HOME=$GRID_HOME "CLUSTER_NODES={host01}"
CRS=TRUE -silent
Now I'll remove that node from the cluster registry.
root $ crsctl delete node -n host02
CRS-4661: Node host02 successfully deleted.
Remove the VIP.
root $ srvctl config vip -node host02
VIP exists: network number 1, hosting node host02
VIP Name: host02-vip
VIP IPv4 Address: 192.168.1.101
VIP IPv6 Address:
VIP is enabled.
VIP is individually enabled on nodes:
VIP is individually disabled on nodes:
root $ srvctl stop vip -vip host02-vip -force
root $ srvctl remove vip -vip host02-vip
Please confirm that you intend to remove the VIPs host02-vip (y/[n]) y
Then remove the instance.
root $ srvctl remove instance -db orcl -instance orcl2
Remove instance from the database orcl? (y/[n]) y
At this point, the bad node is no longer part of the cluster, from the good node's perspective.
Next, I'll move to the bad node and remove the software and clean up some config files.