 |
|
OS commands for RAC
Oracle Database Tips by Donald Burleson
|
Oracle provides the crs and
srvctl command utility for checking on the external
status of RAC databases. For complete details in RAC OS
commands, see the
bestselling book
Oracle Grid & Real Application Clusters.
CRS Commands
Oracle provides a host of cluster ready services commands to
display details about all services running on the CRS.
These CRS commands include:
CRS Command |
Function |
crs_stat: |
Displays CRS resource status |
crsctl check crs |
Check CRS status |
crsctl stop crs |
Stops the CRS and all services |
crsctl disable crs* |
Prevents CRS from autostarting on server bounce |
crsctl enable crs* |
Enables CRS autostart on reboot |
crs_stop all |
Stops all registered CRS resources |
crs_start all |
Starts all registered resources |
|
|
The srvctrl RAC OS Command
The srvctl command replaces
the earlier utility 'opsctl' which was used in the
parallel server.
The Server Control Utility is a single point of control between
the Oracle Intelligent agent and each node in the RAC system.
The SRVCTL communicates with the global daemon service (GSD) and
resides on each of the nodes.
Here are some working example of svrctl commands for RAC
root> srvctl status nodeapps -n u01
root> srvctl status asm -n u01
root> srvctl status service -d
racumup
root> srvctl status database -d
racumup
Here are my srvctl notes:
Using CRS commands at the OS level
The CRS (Cluster Ready Services)
utility is called crsctl and it queries the cluster
details. Oracle10g introducedCluster Ready Services (CRS),
which provides many system management services and interacts
with the vendor clusterware to coordinate cluster membership
information. It provides the cluster software, sometimes called the Oracle OSD Clusterware.
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
The OUI installs CRS on each node on which the OUI detects that
vendor clusterware is running. In addition, the CRS home is
distinct from the RAC-enabled Oracle Home.
root> crsctl check crs
Here are my CRS notes: