{"id":301,"date":"2026-10-13T11:11:15","date_gmt":"2026-10-13T11:11:15","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2011\/08\/04\/oracle-rac-cheat-sheet\/"},"modified":"2026-10-13T11:11:15","modified_gmt":"2026-10-13T11:11:15","slug":"oracle-rac-cheat-sheet","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/oracle-rac-cheat-sheet\/","title":{"rendered":"Oracle RAC Operations Cheat Sheet: CRSCTL, SRVCTL, ASM, OCR, and Network Checks"},"content":{"rendered":"\n

Originally published on 2011-08-04; fully revised and updated.<\/em><\/p>\n\n\n\n

This guide is a field-ready Oracle RAC cheat sheet for DBAs and platform engineers who need quick, reliable operational commands. It covers cluster health checks, start\/stop procedures, database and instance control, and key infrastructure validations (ASM, OCR, voting disk, listener, SCAN, and VIP), using the command patterns from the original post.<\/p>\n\n\n\n

\"Oracle<\/a><\/figure>\n\n\n\n

Command families and when to use them<\/h2>\n\n\n\n
Command family<\/th>Primary use<\/th>Example from this cheat sheet<\/th>Typical execution user<\/th><\/tr><\/thead>
crsctl<\/td>Clusterware stack and cluster-level control<\/td>crsctl check crs<\/td>root (for some stack operations)<\/td><\/tr>
srvctl<\/td>RAC-managed resources (DB, ASM, listener, VIP, SCAN)<\/td>srvctl status database -d racdb<\/td>grid or oracle (environment-dependent)<\/td><\/tr>
ocrcheck \/ cluvfy<\/td>Registry and validation checks<\/td>ocrcheck<\/td>oracle or grid (environment-dependent)<\/td><\/tr>
emctl<\/td>Enterprise Manager DB Console control (legacy)<\/td>emctl status dbconsole<\/td>oracle<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Core cluster health checks<\/h2>\n\n\n\n

Use these first to get a fast view of cluster state and node membership before any maintenance action.<\/p>\n\n\n

# Clusterware stack health<\/span>\ncrsctl check crs\n\n# Clusterware resources overview (legacy command style)<\/span>\ncrs_stat -t -v\n\n# List cluster nodes and node numbers<\/span>\nolsnodes -n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Start and stop Oracle Clusterware<\/h2>\n\n\n\n
These commands are high-impact. Confirm scope (single node<\/strong> vs entire cluster<\/strong>) before execution.<\/p>\n\n\n\n
Local node operations<\/h3>\n\n\n
# Stop Clusterware stack on the local server<\/span>\n\/u01\/app\/11.2<\/span>.0<\/span>\/grid\/bin\/crsctl stop cluster\n\n# Start Clusterware stack on the local server<\/span>\n\/u01\/app\/11.2<\/span>.0<\/span>\/grid\/bin\/crsctl start cluster<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
All node operations<\/h3>\n\n\n
# Stop Clusterware stack on all servers<\/span>\ncrsctl stop cluster -all\n\n# Start Clusterware stack on all servers<\/span>\ncrsctl start cluster -all<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Verify ASM, OCR, and voting disk<\/h2>\n\n\n\n
After startup or maintenance, verify the cluster control plane and storage quorum components.<\/p>\n\n\n
# Confirm ASM status (all ASM instances)<\/span>\nsrvctl status asm -a\n\n# Check Oracle Cluster Registry<\/span>\nocrcheck\n\n# Check voting disk configuration\/status<\/span>\ncrsctl query css votedisk<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Database and instance control with SRVCTL<\/h2>\n\n\n\n
Use SRVCTL for RAC database lifecycle and configuration checks. The examples below use the sample database name racdb<\/strong> from the original article.<\/p>\n\n\n\n
Task<\/th>Command<\/th><\/tr><\/thead>
All Oracle instances (database status)<\/td>srvctl status database -d racdb<\/td><\/tr>
Single Oracle instance status<\/td>srvctl status instance -d racdb -i racdb1<\/td><\/tr>
Stop all instances for the database<\/td>srvctl stop database -d racdb<\/td><\/tr>
Start all instances for the database<\/td>srvctl start database -d racdb<\/td><\/tr>
List all configured databases<\/td>srvctl config database<\/td><\/tr>
Show one database configuration<\/td>srvctl config database -d racdb -a<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
# Typical check-stop-start-verify cycle<\/span>\nsrvctl status database -d racdb\nsrvctl stop database -d racdb\nsrvctl start database -d racdb\nsrvctl status instance -d racdb -i racdb1<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Node applications and network service checks<\/h2>\n\n\n\n
These commands help confirm node-level services and client access paths (listener, SCAN, and VIP).<\/p>\n\n\n
# Node applications<\/span>\nsrvctl status nodeapps\nsrvctl config nodeapps\nsrvctl config nodeapps -a -g -s -l\n\n# Listener and SCAN<\/span>\nsrvctl status listener\nsrvctl status scan\nsrvctl config scan\n\n# VIP checks per node<\/span>\nsrvctl status vip -n racnode1\nsrvctl status vip -n racnode2\nsrvctl config vip -n racnode1\nsrvctl config vip -n racnode2<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Enterprise Manager dbconsole and clock synchronization checks<\/h2>\n\n\n\n
The original cheat sheet includes DB Console commands and cluster time synchronization validation.<\/p>\n\n\n
# Enterprise Manager DB Console (legacy deployments)<\/span>\nemctl status dbconsole\nemctl start dbconsole\nemctl stop dbconsole\n\n# Verify clock synchronization across nodes<\/span>\ncluvfy comp clocksync -verbose<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Recommended RAC maintenance workflow<\/h2>\n\n\n\n
\nflowchart TD\n    A[Run prechecks] --> B{Maintenance scope}\n    B -->|Local node only| C[Stop cluster on local node]\n    B -->|Entire cluster| D[Stop cluster on all nodes]\n    C --> E[Perform maintenance task]\n    D --> E\n    E --> F[Start cluster services]\n    F --> G[Validate database and instance status]\n    G --> H[Verify ASM OCR voting disk and network services]\n    H --> I[Run clock sync validation]\n<\/pre>\n\n\n\n
Best practices and common pitfalls<\/h2>\n\n\n\n