CRSCTL is an action packed program that allows many different
operations related to the clusterware software.
Oracle 11g release 2 introduced
some enhanced crsctl commands to check the CRS status from
any RAC node:
root> crsctl stop
cluster -all
root> crsctl start cluster -all
root> crsctl check cluster -all
These crsctl operations include the enabling/disabling of
clusterware on startup, replacing or moving voting disks, checking
the viability of the cluster, and advanced debugging.
The
crsctl command by itself prints the specifications of
the program:
Usage: crsctl check crs - checks the viability of
the Oracle Clusterware
crsctl check cssd
- checks the viability of Cluster Synchronization Services
crsctl check crsd
- checks the viability of Cluster Ready Services
crsctl check evmd
- checks the viability of Event Manager
crsctl check cluster [-node <nodename>] -
checks the viability of CSS across nodes
crsctl set css <parameter> <value> - sets
a parameter override
crsctl get css <parameter> - sets the
value of a Cluster Synchronization Services parameter
crsctl unset css <parameter> - sets the
Cluster Synchronization Services parameter to its default
crsctl query css votedisk - lists the
voting disks used by Cluster Synchronization Services
crsctl add css votedisk <path> - adds a
new voting disk
crsctl delete css votedisk <path> -
removes a voting disk
crsctl enable crs - enables startup for
all Oracle Clusterware daemons
crsctl disable crs - disables startup for
all Oracle Clusterware daemons
crsctl start crs [-wait] - starts all
Oracle Clusterware daemons
crsctl stop crs [-wait] - stops all Oracle
Clusterware daemons. Stops Oracle Clusterware managed resources in
case of cluster.
crsctl start resources - starts Oracle
Clusterware managed resources
crsctl stop resources - stops Oracle
Clusterware managed resources
crsctl debug statedump css - dumps state
info for Cluster Synchronization Services objects
crsctl debug statedump crs - dumps state
info for Cluster Ready Services objects
crsctl debug statedump evm - dumps state
info for Event Manager objects
crsctl debug log css [module:level] {,module:level}
... - turns on debugging for Cluster Synchronization Services
crsctl debug log crs [module:level] {,module:level}
... - turns on debugging for Cluster Ready Services
crsctl debug log evm [module:level] {,module:level}
... - turns on debugging for Event Manager
crsctl debug log res [resname:level] ... -
turns on debugging for Event Manager
crsctl debug trace css [module:level] {,module:level}
... - turns on debugging for Cluster Synchronization Services
crsctl debug trace crs [module:level] {,module:level}
... - turns on debugging for Cluster Ready Services
crsctl debug trace evm [module:level] {,module:level}
... - turns on debugging for Event Manager
crsctl query crs softwareversion [<nodename>]
- lists the version of Oracle Clusterware software installed
crsctl query crs activeversion - lists the
Oracle Clusterware operating version
crsctl lsmodules css - lists the Cluster
Synchronization Services modules that can be used for debugging
crsctl lsmodules crs - lists the Cluster
Ready Services modules that can be used for debugging
crsctl lsmodules evm - lists the Event
Manager modules that can be used for debugging
If necessary any of these commands can be run with
additional tracing by adding a 'trace'
argument
at the very front. Example: crsctl trace check css
The various
crsctl check commands are very useful when resources do
not start up, or the cluster is suffering from stability issues.
crsctl query css votedisk,
crsctl add css votedisk <path>, and
crsctl delete css votedisk <path> are useful when it is
necessary to move the voting disk location.
Remember that there may be no more than three copies of the
voting disk.
Example:
[root@racnode1 bin]# crsctl add css votedisk /dev/sdg
-force
TIP:
Arguably, some of the most useful commands are the
enable crs and
disable crs commands.
When the crsctl
disable crs command is run, the cluster will be disabled on
startup. If any
maintenance must be run on a cluster, this command is great to
make sure no cluster components start on the system.
