I had been puzzled by the differences between "crsctl ... crs" and "crsctl ... cluster", so I decided to look into the differences between them, it turns out that they are clearly explained in the documentation:
Oracle® Clusterware Administration and Deployment Guide
11g Release
2 (11.2)
Part Number E16794-14
E CRSCTL Utility Reference
According to the above doc:
CRSCTL Overview
CRSCTL is an interface between you and Oracle Clusterware, parsing and
calling Oracle Clusterware APIs for Oracle Clusterware objects.
Oracle Clusterware 11g release 2 (11.2) introduces
cluster-aware commands with which you can perform check, start, and stop
operations on the cluster. You can run these commands from any node in the
cluster on another node in the cluster, or on all nodes in the cluster,
depending on the operation.
You can use CRSCTL commands to perform several operations on Oracle
Clusterware, such as:
-
Starting and stopping Oracle Clusterware resources
-
Enabling and disabling Oracle Clusterware daemons
-
Checking the health of the cluster
-
Managing resources that represent third-party applications
-
Integrating Intelligent Platform Management Interface (IPMI) with Oracle
Clusterware to provide failure isolation support and to ensure cluster
integrity
-
Debugging Oracle Clusterware components
Clusterized (Cluster Aware) Commands
You can run clusterized commands on one node to perform operations on another
node in the cluster. These are referred to as remote operations. This simplifies
administration because, for example, you no longer have to log in to each node
to check the status of the Oracle Clusterware on all of your nodes.
Clusterized commands are completely operating system independent; they rely
on the OHASD (Oracle High Availability Services daemon). If this daemon is
running, then you can perform remote operations, such as the starting, stopping,
and checking the status of remote nodes.
Clusterized commands include the following:
-
crsctl check cluster
-
crsctl start cluster
-
crsctl stop cluster
---crsctl command help shows the following .
crsctl stop cluster
-h
Usage:
crsctl stop cluster [[-all]|[-n [...]]]
[-f]
Stop CRS stack
where
Default Stop local server
-all Stop all
servers
-n Stop named servers
server [...] One or more blank-separated
server names
-f Force option
In simple words it work
like this.
crsctl stop cluster is equal to crsctl stop crs
crsctl
stop cluster -all --> stops clsuterware on ALL nodes.
crsctl stop cluster
-n racnode1 stops clusterware on node racnode1.
Labels: 11202, CRS, crsctl, RAC
