CRSCTL

Find below various commands which can be used to administer Oracle Clusterware using crsctl.


There are options for CRSCTL which can be seen using the fllowing command



#crsctl

Or

#crsctl help



To determine software version (binary version of the software/operating version on a particular cluster node) use


#crsctl query crs softwareversion [] - lists the version of CRS software installed

Oracle Clusterware version on node [Rac01] is [x.x.x.x.x]


#crsctl query crs activeversion - lists the CRS software operating version

Oracle Clusterware active version on the cluster is [x.x.x.x.x]


Start Oracle Clusterware --> #crsctl start crs


Stop Oracle Clusterware --> #crsctl stop crs


Enable Oracle Clusterware --> #crsctl enable crs


It enables automatic startup of Clusterware daemons


Disable Oracle Clusterware --> #crsctl disable crs

NOTE:- 1) This command disables OC from being started in
a subsequent restart
2) This Does not stop the currently running OC Stack




@===== Check CRS Status =====@


#crsctl check crs

Cluster Synchronization Services appears healthy
Cluster Ready Services appears healthy
Event Manager appears healthy



@===== To see particular daemon status =====@


$crsctl check cssd

Cluster Synchronization Services appears healthy


$crsctl check crsd

Cluster Ready Services appears healthy


$crsctl check evmd

Event Manager appears healthy


You can also check Clusterware status on the nodes using



$crsctl check cluster

Rac01 ONLINE
Rac02 ONLINE
..... ......



@===== Checking Voting disk Location =====@


$crsctl query css votedisk
0. 0 /dev/sda3
1. 0 /dev/sda5
2. 0 /dev/sda6

Located 3 voting disk(s).



Note: -Any command which just needs to query information can be run using oracle user. But anything which alters Oracle Clusterware requires root privileges.



Add Voting disk --> #crsctl add css votedisk path



Remove Voting disk --> #crsctl delete css votedisk path




@===== Enabling Debugging of Oracle Clusterware Components =====@



You can enable debugging for the Oracle Cluster daemons by running crsctl commands [debugging_level is a number from 1 to 5]



# crsctl debug log component module:debugging_level


To enable tracing for the EVMD module of the css component, you could use the following command:


# crsctl debug log css EVMD:1



@===== Locating the Oracle Clusterware Alert Log =====@


The location of the Oracle Clusterware log file is CRS_home/log/hostname/alerthostname.log, where CRS_home is the directory in which Oracle Clusterware was installed and hostname is the host name of the local node

To obtain a list of the resources available for debugging, use the following command:


# crs_stat

=====@@@@@@@@@@@@@@@@@@@=====

USAGE
============================

crsctl
Usage: crsctl check crs - checks the viability of the CRS stack
crsctl check cssd - checks the viability of CSS
crsctl check crsd - checks the viability of CRS
crsctl check evmd - checks the viability of EVM
crsctl set css - sets a parameter override
crsctl get css - gets the value of a CSS parameter
crsctl unset css - sets CSS parameter to its default
crsctl query css votedisk - lists the voting disks used by CSS
crsctl add css votedisk - adds a new voting disk
crsctl delete css votedisk - removes a voting disk
crsctl enable crs - enables startup for all CRS daemons
crsctl disable crs - disables startup for all CRS daemons
crsctl start crs - starts all CRS daemons.
crsctl stop crs - stops all CRS daemons. Stops CRS resources in case of cluster.
crsctl start resources - starts CRS resources.
crsctl stop resources - stops CRS resources.
crsctl debug statedump evm - dumps state info for evm objects
crsctl debug statedump crs - dumps state info for crs objects
crsctl debug statedump css - dumps state info for css objects
crsctl debug log css [module:level]{,module:level} ...


- Turns on debugging for CSS

crsctl debug trace css - dumps CSS in-memory tracing cache
crsctl debug log crs [module:level]{,module:level} ...

- Turns on debugging for CRS

crsctl debug trace crs - dumps CRS in-memory tracing cache
crsctl debug log evm [module:level]{,module:level} ...

- Turns on debugging for EVM

crsctl debug trace evm - dumps EVM in-memory tracing cache
crsctl debug log res turns on debugging for resources
crsctl query crs softwareversion [] - lists the version of CRS software installed
crsctl query crs activeversion - lists the CRS software operating version
crsctl lsmodules css - lists the CSS modules that can be used for debugging
crsctl lsmodules crs - lists the CRS modules that can be used for debugging
crsctl lsmodules evm - lists the EVM modules that can be used for debugging

If necesary any of these commands can be run with additional tracing by
adding a "trace" argument at the very front.

Example: crsctl trace check css


Vijay Kumar....