Which two steps must always be performed to delete node host04 from an Oracle 12c Clusterware cluster that does not use Grid Naming Service (GNS)?

A.
Run the crsctl unpin css – host04 command as root on host01, or on either host02 or host03.

B.
Run the rootcrs.pl – delete –force command as root on host01, or on either host02 or host03.

C.
Run the rootcrs.pl – delete –force command as root on host04.

D.
Run the crsctl delete node -n host04 command as root on host04.

E.
Run the crsctl delete node -n host04 command as root on host04.

F.
Run the crsctl delete node -n host04 command as root on host01, or on either host02 or host03.

Explanation:

To delete a node from a cluster:
1. Ensure that Grid_home correctly specifies the full directory path for the Oracle Clusterware home on each node, where Grid_home is the location of the installed
Oracle Clusterware software.
2. (A) Run the following command as either root or the user that installed Oracle Clusterware to determine whether the node you want to delete is active and
whether it is pinned:
$ olsnodes -s –t
If the node is pinned, then run the crsctl unpin css command. Otherwise, proceed to the next step.
3. (F) From any node that you are not deleting, run the following command from the Grid_home/bin directory as root to delete the node from the cluster:
# crsctl delete node -n node_to_be_deleted
https://docs.oracle.com/database/121/CWADD/adddelclusterware.htm#CWADD90992

Show Hint

← Previous question

Next question →

WGCM

I really doesn’t know…

https://docs.oracle.com/database/121/CWADD/adddelclusterware.htm#CWADD90997
7 Adding and Deleting Cluster Nodes
Adding and Deleting Cluster Nodes on Linux and UNIX Systems

To delete a node from a cluster:

1. Ensure that Grid_home correctly specifies the full directory path for the Oracle Clusterware home on each node, where Grid_home is the location of the installed Oracle Clusterware software.

2. Run the following command as either root or the user that installed Oracle Clusterware to determine whether the node you want to delete is active and whether it is pinned:

$ olsnodes -s -t

“”If the node is pinned””, then run the “crsctl unpin css” command. Otherwise, proceed to the next step.

3. On the node you want to delete, run the following command as the user that installed Oracle Clusterware from the Grid_home/oui/bin directory where node_to_be_deleted is the name of the node that you are deleting:
$ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home “CLUSTER_NODES={node_to_be_deleted}” CRS=TRUE -silent -local

4. On the node that you are deleting, depending on whether you have a shared or local Oracle home, complete one of the following procedures as the user that installed Oracle Clusterware:

■ For a local home, deinstall the Oracle Clusterware home from the node that you want to delete, as follows, by running the following command, where Grid_home is the path defined for the Oracle Clusterware home:

$ Grid_home/deinstall/deinstall -local

***************************
Caution:
■ If you do not specify the -local flag, then the command removes the Oracle Grid Infrastructure home from every node in the cluster.
■ If you cut and paste the preceding command, then paste it into a text editor before pasting it to the command line to remove any formatting this document might contain.
***************************

■ “”If you have a shared home””, then run the following commands in the following order on the node you want to delete.

Run the following command to deconfigure Oracle Clusterware:
$ Grid_home/perl/bin/perl Grid_home/crs/install/rootcrs.pl -deconfig -force

Run the following command from the Grid_home/oui/bin directory to detach the Grid home:
$ ./runInstaller -detachHome ORACLE_HOME=Grid_home -silent -local

■ Manually delete any configuration files, as prompted by the installation utility.

5. On any node other than the node you are deleting (except for a Leaf Node in an Oracle Flex Cluster), run the following command from the Grid_home/oui/bin directory where remaining_nodes_list is a comma-delimited list of the nodes that are going to remain part of your cluster:
$ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home “CLUSTER_NODES={remaining_nodes_list}” CRS=TRUE -silent

***************************
Notes:
■ You must run this command a second time from the Oracle RAC home, where ORACLE_HOME=ORACLE__RAC_HOME and CRS=TRUE -silent is omitted from the syntax, as follows:
$ ./runInstaller -updateNodeList ORACLE_HOME=ORACLE_HOME “CLUSTER_NODES={remaining_nodes_list}”
■ Because you do not have to run this command if you are deleting a Leaf Node from an Oracle Flex Cluster, remaining_nodes_list must list only Hub Nodes.
■ If you have a shared Oracle Grid Infrastructure home, then append the -cfs option to the command example in this step and provide a complete path location for the cluster file system.
***************************

6. “”From any node that you are not deleting””, run the following command from the Grid_home/bin directory as root to delete the node from the cluster:
# crsctl delete node -n node_to_be_deleted

crsctl unpin css
Use the crsctl unpin css command to unpin many servers. If a node is not pinned, its node number may change if the lease expires while it is down.

Syntax
crsctl unpin css -n node_name [node_name […exit]]

Usage Notes
■ You can specify a space-delimited list of nodes.
■ Unpinned servers that stop for longer than a week are no longer reported by olsnodes. These servers are dynamic when they leave the cluster, so you do not need to explicitly remove them from the cluster.
■ Deleting a node with the “crsctl delete node” command “implicitly unpins the node”.
■ During upgrade of Oracle Clusterware, all servers are pinned, whereas after a fresh installation of Oracle Clusterware 12c, all servers you add to the cluster are unpinned.