7 Deinstallation of Oracle Clusterware

7.3.1 About the rootdelete.sh Script

The rootdelete.sh script should be run from the Oracle Clusterware home on each node. It stops the Oracle Clusterware stack, removes inittab entries, and deletes Oracle Clusterware files. It can also be used to downgrade the Oracle Cluster Registry from the existing release to a previous release. The script uses the following syntax:

# rootdelete.sh options

Options:

• paramfile: Use a parameter file containing configuration information for the rootdelete.sh command. Provide the path and name of the parameter file. For example: -paramfile /usr/oracle/cwdeletepar.

• local|remote: Use local if you are running rootdelete.sh on the local node, and use remote if you are running the script on one of the other nodes. The local node is the one from which you run OUI (in other words, the last surviving node), and on which you run rootdeinstall.sh.

• nosharedvar|sharedvar: Use nosharedvar if the directory path for ocr.loc (in /etc/oracle or /var/opt/oracle) is not on a shared filesystem. Use sharedvar if the directory path for ocr.loc is in a shared location. The default is nosharedvar.

• sharedhome|nosharedhome: Use sharedhome if the Oracle Clusterware home is shared across the nodes. Otherwise, use nosharedhome. The default is sharedhome.

• downgrade: Use this option if the Oracle Clusterware is downgraded to a previous Oracle Clusterware version. The -downgrade option takes the following flags:

  • -version: Use this option to specify the version to which you want to downgrade. The default is 10.2.

  • -force: Use this option to force cleanup of root configuration

For example, to run the rootdelete.sh script from an Oracle Clusterware home in the path /u01/app/crs, where you are running the script on a remote node, and the ocr.loc file is in /etc/oracle on each node, enter the following command:

# cd /u01/app/crs/install/
# ./ rootdelete.sh remote nosharedvar

7.3.2 Example of the rootdelete.sh Parameter File

You can create a parameter file for rootdelete.sh to repeat deinstallation steps. You may want to do this if you intend to perform repeated reinstallations, as in a test environment. The following is an example of a parameter file for rootdelete.sh; terms that change relative to system configuration are indicated with italics:

CLUSTER_NODES=mynode1,mynode2
INVENTORY_LOCATION=u01/app/oracle/oraInventory
CRS_HOME=true
ORA_CRS_HOME=/u01/app/crs
ORACLE_OWNER=oracle
DBA_GROUP=oinstall

7.3.3 About the rootdeinstall.sh Script

The rootdeinstall.sh script should be run on the local node only, after rootdelete.sh has been run on all nodes of the cluster. Use this command either to remove the Oracle Clusterware OCR file, or to downgrade your existing installation. The rootdeinstall.sh script has the following command options:

• paramfile: A parameter file containing configuration information for the rootdelete.sh command

• downgrade: Use this option if the database is downgraded to a previous Oracle Clusterware version. Use the -version flag to specify the version to which you want to downgrade. The default is 10.2.

7.3.4 Removing Oracle Clusterware

Stop all Oracle processes except for Oracle Clusterware, as described in Appendix B, in the section "How to Stop Processes in an Existing Oracle Database". Then run the following scripts in order from the CRS_home/install directory, using the appropriate options:

rootdelete.sh
rootdeinstall.sh

For example:

[root@node1 /]# cd /u01/app/crs/install
[root@node1 install]# ./rootdelete.sh local nosharedvar -paramfile /home/ 
crs/deconfig.param
Reading /home/crs/deconfig.param..
File (/home/crs/deconfig.param) is used for setting CRS variables.
ORA_CRS_HOME=/u01/app/crs
ORACLE_OWNER=oracle
DBA_GROUP=oinstall
Getting local node name
NODE = node1
Getting local node name
NODE = node1
Stopping VIPs that are still up
Getting cluster node names
Cluster Nodes = node1
node2
Stopping vip
Stopping resources.
This could take several minutes
Successfully stopped Oracle Clusterware resources
Shutting down the Cluster Synchronization Services daemon.
Shutdown request successfully issued.
Waiting for Cluster Synchronization Services daemon to stop
Cluster Synchronization Services daemon has stopped
Oracle CRS stack is not running.
Oracle CRS stack is down now
Removing script for Oracle Cluster Ready services
Updating ocr file for downgrade
Cleaning up SCR settings in '/etc/oracle/scls_scr'
Cleaning up NS directories
[root@node1 install]# ssh docrac2
[root@node2 /] cd /u01/app/crs/install
[root@node2 install]# ./rootdelete.sh remote nosharedvar -paramfile /home/crs/deconfig.param
Reading /home/crs/deconfig.param..
Getting local node name
ORA_CRS_HOME=/u01/app/crs
ORACLE_OWNER=oracle
DBA_GROUP=oinstall
Getting local node name
NODE = node2
Getting local node name
NODE = node2
Getting cluster node names
Cluster Nodes = node1
node2
Stopping vip
Stopping resources.
Shutting down Oracle Cluster Ready Services (CRS):
Stopping resources.
This could take several minutes.
Successfully stopped Oracle Clusterware resources
Shutting down the Cluster Synchronization Services daemon.
Shutdown request successfully issued.
Shutdown has begun. The daemons should exit soon.
Checking to see if Oracle CRS stack is down...
Oracle CRS stack is not running.
Oraacle CRS stack is down now
Removing script for Oracle Cluster Ready services
Updating ocr file for downgrade
Cleaning up SCR settings in '/etc/oracle/scls_scr'
Cleaning up NS directories
[root@node2 install]# exit
[root@node1 install]# ./rootdeinstall.sh