We might encounter an error on one or more cluster nodes during installation when running the root.sh command, such as a missing operating system package on one node. By running “rootcrs.sh -deconfig -force” on nodes where you encounter an installation error, you can unconfigure Oracle Clusterware on those nodes, correct the cause of the error, and then run root.sh again.
[root@racnode1 install]# cd /u01/app/18.0.0/grid/crs/install [root@racnode1 install]# ./rootcrs.sh -deconfig -force Using configuration parameter file: /u01/app/18.0.0/grid/crs/install/crsconfig_params The log of current session can be found at: /u01/app/grid/crsdata/racnode1/crsconfig/crsdeconfig_racnode1_2020-03-12_09-58-18PM.log PRCR-1070 : Failed to check if resource ora.net1.network is registered CRS-0184 : Cannot communicate with the CRS daemon. PRCR-1070 : Failed to check if resource ora.helper is registered CRS-0184 : Cannot communicate with the CRS daemon. PRCR-1070 : Failed to check if resource ora.ons is registered CRS-0184 : Cannot communicate with the CRS daemon. 2020/03/12 21:58:25 CLSRSC-180: An error occurred while executing the command '/u01/app/18.0.0/grid/bin/srvctl config nodeapps' 2020/03/12 21:58:36 CLSRSC-336: Successfully deconfigured Oracle Clusterware stack on this node
[root@racnode1 install]# ls -ltr /u01/app/grid/crsdata/racnode1/crsconfig/crsdeconfig_racnode1_2020-03-12_09-58-18PM.log -rw-rw-r-- 1 grid oinstall 45152 Mar 12 21:58 /u01/app/grid/crsdata/racnode1/crsconfig/crsdeconfig_racnode1_2020-03-12_09-58-18PM.log [root@racnode1 install]#
Make DBA Life Easy 