Clusterware Stack Management and Troubleshooting - Expert Oracle RAC 12c - page 38

Start the Oracle High Availability Services daemon ( OHASD ) and the Clusterware service stack together on the
local server only:
$crsctl start crs
Both of these two crsctl startup commands require the root privilege on Linux/Unix to run. The 'crsctl start
crs' command will fail if OHASD is already started.
The crsctl utility also provides similar commands to stop the Oracle Clusterware manually. It also requires root
privilege on Linux/Unix to stop the clusterware manually.
The following command stops the clusterware stack on the local node, or all nodes, or specified local or
remote nodes. Without the [-f] option, this command stops the resources gracefully, and with the [-f] option, the
command forces the Oracle Clusterware stack to stop, along with the resources that Oracle Clusteware manages.
$ crsctl stop cluster [-all | -n server_name [...]] [-f]
The following command stops the Oracle High Availability service on the local server. Use the [-f] option to
force any resources to stop, as well as to stop the Oracle High Availability service:
$ crsctl stop crs [-f]
Managing Oracle Clusterware
You can use the following command to check the cluster status:
$ crsctl check cluster {-all}
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
Check the CRS status with the following command:
$ crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
Check the OHASD status:
$GRID_HOME/bin/crsctl check has
CRS-4638: Oracle High Availability Services is online
Check the current status of all the resources using the following command. It replaces the crs_stat -t
command on 11gR1 and earlier.