Steps to remove Node from Cluster when the Node crashes due to OS/Hardware failure and cannot boot up
(Doc ID 466975.1)
Last updated on APRIL 12, 2024
Applies to:
Oracle Database Backup Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.6 [Release 10.2 to 11.1]
Oracle Database - Standard Edition - Version 10.2.0.1 to 11.1.0.6 [Release 10.2 to 11.1]
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.2.0.1 to 11.1.0.6
Oracle Clusterware
Goal
This document is intended 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. 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 cluster-ware commands from this node.
For 11gR2, refer to <note 1262925.1>
Solution
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
Goal |
Solution |
Summary |
Example Configuration |
Initial Stage |
Step 1 Remove oifcfg information for the failed node |
Step 2 Remove ONS information |
Step 3 Remove resources |
Step 4 Execute rootdeletenode.sh |
Step 5 Update the Inventory |
References |