How to Remove/Delete a Node From Grid Infrastructure Clusterware When the Node Has Failed
(Doc ID 1262925.1)
Last updated on JULY 13, 2022
Applies to:Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This document is intented to provide the steps to be taken to remove a node from the Oracle cluster.
The node itself is unavailable due to some OS issue or hardware issue which prevents the node from starting up.
It is also possible to use this note to remove the node and add it back in situations where the GRID home has been corrupted and the clusterware needs to be rebuilt from the ground up on the problem node.
This document will provide the steps to remove such a node so that it can be added back after the node is fixed.
The steps to remove a node from a Cluster is already documented in the Oracle documentation at
This note is different because the documentation covers the scenario where the node is accessible and the removal is a planned procedure.
This note covers the scenario where the Node is unable to boot up and therefore it is not possible to run the clusterware commands from this node.
Please note that after using the information provided here to remove the 'problem' node, if it is subsequently restarted at a later date, it will rejoin the Cluster.
This fact has been reported under internal bug:17058972 - Development are currently considering this bug.
For 10gR2 or 11gR1, refer to <note 466975.1>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Removing a Node from an 11.2 Cluster where the node no longer exists.|
|1. Reconfigure the RDBMS Services in the cluster to take into account node 2 is gone.|
|2. Reconfigure the RDBMS Instances in the cluster to take into account node 2 is gone.|
|3. Remove the Node from the RAC Cluster|
|4. Remove the Node from the Grid Cluster|