Introduction
Oracle Real Application Clusters (RAC) is a powerful database technology that provides high availability and scalability. To ensure a smooth startup of your Oracle RAC database, it’s essential to follow a proper sequence of commands. In this guide, we’ll walk you through the right procedure of RAC database startup.
How to Startup Oracle Real Application Clusters Database ?
- Start Oracle Clusterware / CRS.
- Start Node applications on all nodes.
- Start ASM instances from all nodes.
- Start RAC Database Instances on all nodes.
- Start Oracle Listener.
1. Start Oracle Clusterware / CRS
##Go to $GRID_HOME/bin directory through root user##
[root@node1 bin]# pwd
/u01/app/12.2.0/grid/bin
##Start Cluster on Both nodes one by one##
[root@node1 bin]# ./crsctl start crs
CRS-4123: Oracle High Availability Services has been started
[root@node2 bin]# ./crsctl start crs
CRS-4123: Oracle High Availability Services has been started
##Start ora.crsd resource if you get error mentioned in Note below##
[root@node1 bin]# ./crsctl start res ora.crsd -init
##To Check Cluster Status of All Nodes##
[root@node1 bin]# ./crsctl check cluster -all
**************************************************************
node1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
*************************************************************
node2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
NOTE(Important):
============================================================
Sometime we get following error message:
CRS-4639: Could not contact Oracle High Availability Services
OR
CRS-4535: Cannot communicate with Cluster Ready Services
Wait for few minutes and then again check with “crsctl check cluster -all” command.
Now we will get “CRS-4537: Cluster Ready Services is online”.
If still same issue persists then we can start ora.crsd process to resolve this issue.
Below is the command:
[root@node1 bin]# ./crsctl start res ora.crsd -init
============================================================
2. Start Node applications on all nodes
##To Start Nodeapps on all Nodes##
[grid@node1 ~]$ srvctl start nodeapps
##It has to executed on each node##
##To Check Status of Nodeapps on all Nodes##
[grid@node1 ~]$ srvctl status nodeapps
VIP 192.168.1.73 is enabled
VIP 192.168.1.73 is running on node: node1
VIP 192.168.1.74 is enabled
VIP 192.168.1.74 is running on node: node2
Network is enabled
Network is running on node: node1
Network is running on node: node2
ONS is enabled
ONS daemon is running on node: node1
ONS daemon is running on node: node2
##OTHER COMMANDS##
##To Start nodeapps on particular node ##
[grid@node1 ~]$ srvctl start nodeapps -n node1
##To Check status of specific node nodeapps##
[grid@node1 ~]$ srvctl status nodeapps -n node1
VIP 192.168.1.73 is enabled
VIP 192.168.1.73 is running on node: node1
Network is enabled
Network is running on node: node1
ONS is enabled
ONS daemon is running on node: node1
3. Start ASM instances from all nodes.
##To Start ASM instances on all Nodes##
[grid@node1 ~]$ srvctl start asm
##To Check Status of ASM instances on all Nodes##
[grid@node1 ~]$ srvctl status asm
ASM is running on node1,node2
##OTHER COMMANDS##
##To Stop any specific ASM instance ##
[grid@node1 ~]$ srvctl start asm -n node1
##To Check status of any specific ASM instance ##
[grid@node1 ~]$ srvctl status asm -n node1
ASM is not running on node14. Start RAC Database Instances on all nodes.
##To Stop database instances on all Nodes##
##Execute this command from any node having database, it will start all database instances on all servers##
[oracle@node1 ~]$ srvctl start database -d DBPROD
##To Check database instances Status of all Nodes##
[oracle@node1 ~]$ srvctl status database -d DBPROD
Instance DBPROD1 is not running on node node1
Instance DBPROD2 is not running on node node2
##OTHER COMMANDS##
##To Start any specific database instance ##
[oracle@node1 ~]$ srvctl start instance -d DMRPROD -i DMPROD1
##To Check status of any specific database instance ##
[oracle@node1 ~]$ srvctl status instance -d DMRPROD -i DMPROD2
Instance DMPROD2 is running on node node25. Start Oracle Listener
##To start listener from all nodes##
[grid@node1 ~]$ srvctl start listener
##To Check Status of listener##
[grid@node1 ~]$ srvctl status listener
Listener LISTENER is enabled
Listener LISTENER is not running on node(s): node1,node2
##OTHER COMMANDS##
##To start listener of a particular node##
[grid@node1 ~]$ srvctl start listener -n node1
##To check listener status of a particular node##
[grid@node1 ~]$ srvctl status listener -n node1
Listener LISTENER is enabled on node(s): node1
Listener LISTENER is not running on node(s): node1Conclusion
RAC database startup procedure in the correct sequence is crucial for ensuring its stability and availability. By following these steps, you’ll be able to start your Oracle RAC database, its services, and instances systematically. Always make sure to refer to Oracle’s official documentation for any specific requirements related to your database version and configuration.
RAC Database Shutdown Procedure
