Blog
Start and Stop RAC Services
How to Shutdown and startup Oracle Real Application Clusters Database :
STOP ORACLE RAC 1. emctl stop dbconsole 2. srvctl stop listener -n rac1 3. srvctl stop database -d rac 4. srvctl stop asm -n rac1 -f 5. srvctl stop asm -n rac2 -f 6. srvctl stop nodeapps -n rac1 -f 7. crsctl stop crs
START ORACLE RAC 1. crsctl start crs 2. crsctl start res ora.crsd -init 3. srvctl start nodeapps -n rac1 4. srvctl start nodeapps -n rac2 5. srvctl start asm -n rac1 6. srvctl start asm -n rac2 7. srvctl start database -d rac 8. srvctl start listener -n rac1 9. emctl start dbconsole
Stop Oracle Real Application Clusters
1. Stop Oracle Home LISTENER
srvctl stop listener -n rac1
srvctl status listener -n rac1
Listener LISTENER is enabled on node(s): rac1
Listener LISTENER is not running on node(s): rac1
2. Shutdown RAC Database Instances on all nodes
Syntax: srvctl stop database -d {databasename}
srvctl status database -d rac
Instance rac1 is running on node rac1
Instance rac2 is running on node rac2
srvctl stop database -d rac
srvctl status database -d rac
Instance rac1 is not running on node rac1
Instance rac2 is not running on node rac2
Execute one command from any one of the server having database and it will stop all database instances on all servers.
3. Shutdown All ASM instances from all nodes
Syntax: srvctl stop asm -n {node}
srvctl stop asm -n rac1 -f
srvctl stop asm -n rac2 -f
Check Status
srvctl status asm -n rac1
ASM is not running on rac1
srvctl status asm -n rac2
ASM is not running on rac2
Sometimes, we may face some issues in stopping ASM instance, In that case use “-f” option to forcefully shutdown ASM instances.
4. Shutdown Node applications running on nodes
srvctl stop nodeapps -n rac1 -f
srvctl status nodeapps -n rac1
VIP rac1-vip is enabled
VIP rac1-vip is running on node: rac1
Network is enabled
Network is running on node: rac1
GSD is disabled
GSD is not running on node: rac1
ONS is enabled
ONS daemon is running on node: rac1
Repeat same command for all nodes one by one. If you face any issue in stopping node applications use “-f” as force option to stop applications.
- Shut down the Oracle Clusterware or CRS In this command all CRS related process will be stopped.
This needs to be executed by “root” user on all database nodes.
crsctl check cluster -all
rac1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
rac2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
crsctl stop crs
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘rac1’
CRS-2673: Attempting to stop ‘ora.crsd’ on ‘rac1’
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on ‘rac1’
CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN2.lsnr’ on ‘rac1’
CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘rac1’
CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN3.lsnr’ on ‘rac1’
CRS-2673: Attempting to stop ‘ora.rac2.vip’ on ‘rac1’
CRS-2677: Stop of ‘ora.cssd’ on ‘rac1’ succeeded
CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘rac1’
CRS-2677: Stop of ‘ora.gipcd’ on ‘rac1’ succeeded
CRS-2673: Attempting to stop ‘ora.gpnpd’ on ‘rac1’
CRS-2677: Stop of ‘ora.gpnpd’ on ‘rac1’ succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘rac1’ has completed
CRS-4133: Oracle High Availability Services has been stopped.
crsctl check cluster -all
CRS-4639: Could not contact Oracle High Availability Services
CRS-4000: Command Check failed, or completed with errors.
Start Oracle Real Application Clusters Database
- Start Oracle Clusterware or CRS: CRS starts automatically when you start or restart Server
This needs to be executed by “root” user on all nodes.
crsctl start crs
CRS-4123: Oracle High Availability Services has been started
crsctl check cluster -all
rac1:
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
rac2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
If we see “CRS-4639: Could not contact Oracle High Availability Services” or “CRS-4535: Cannot communicate with Cluster Ready Services” messages. Wait 5 minutes and then again check with “crsctl check cluster -all” command. This time Database administrator will get “CRS-4537: Cluster Ready Services is online”. If still same issue DBA can start ora.crsd process to resolve this issue. Below is the command
crsctl start res ora.crsd -init
crsctl check cluster -all
rac1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
rac2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
Now, Cluster is up and running. DBA can also use “ps -ef | grep d.bin” to check cluster status.
ps -ef | grep d.bin
crsctl check cluster -all
ps -ef | grep d.bin
2. Start Node applications running on nodes
srvctl start nodeapps -n rac1
srvctl status nodeapps -n rac1
VIPrac1-vip is enabled
VIPrac1-vip is running on node:rac1
Network is enabled
Network is running on node:rac1
GSD is disabled
GSD is not running on node:rac1
ONS is enabled
ONS daemon is running on node:rac1
srvctl status nodeapps -n rac2
Execute this command for each node to start RAC Cluster database.
3. Start All ASM instances from all nodes
srvctl start asm -n rac1
srvctl status asm -n rac1
ASM is running on rac1
srvctl status asm -n rac2
DBA has to start ASM instance on all database nodes.
4. Start RAC Database Instances on all nodes
srvctl start database -d rac
srvctl status database -d rac
Instance rac1 is running on rac1
Instance rac2 is running on rac2
Now database is up and running on both DB nodes.
srvctl status database -d rac
5. Start Oracle Home LISTENER
srvctl start listener -n rac1
srvctl status listener -n rac1
Listener LISTENER is enabled on node(s):rac1
Listener LISTENER is running on node(s):rac1
srvctl status listener -n rac2
Hope it Helps,