Shutdown RAC

How to Shutdown and Start Oracle Real Application Clusters Database - These 10 Easy Steps

 

Shutdown and Start Oracle Real Application Clusters Database is any activity, which is performed by DBA for Applying CRS patch, Scheduled maintenance and adding more products in to Real Application Cluster. Since, RAC involves so many components like Database instance, ASM instance, Node application and CRS services, So Start or Shut down Oracle Real Application Clusters Database involved series of steps.

 

An important factor to consider by DBA while start or shutdown Oracle RAC Database is that steps must be performed in specific suggested order otherwise database can go into inconsistency. In this post, I will explain each step one by one and after performing steps we will also cross check for same operation. Let's start with. 

è How to Shutdown Oracle Real Application Clusters Database?

Here, We will start with stopping resources from Enterprise Manager Grid Control to Oracle Cluster ware or CRS process and will end at stopping CRS services. Here I am taking an example of Two node RAC database to perform all operations. Steps followed are as:

 

1.  Shutdown Oracle Home process accessing database.

 

2.  Shutdown RAC Database Instances on all nodes.

 

3.  Shutdown All ASM instances from all nodes.

 

4.  Shutdown Node applications running on nodes.

 

5.  Shut down the Oracle Cluster ware or CRS.

1.  Shutdown Oracle Home process accessing database:

 

There could be oracle and non Oracle application which access database, So first step is to stop all the applications or DBA should inform application owner and he should stop all applications accessing Database. DBA should also stop Oracle application like Enterprise Manager Grid Control and Database Listener which access database for monitoring and database connections.

 

[oracle@database ~]$ emctl stop dbconsole

Oracle Enterprise Manager 11g Database Control Release 11.2.0.2.0

Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.

https://database.example.com:5500/em/console/aboutApplication

Stopping Oracle Enterprise Manager 11g Database Control ...

 ...  Stopped.

[grid@node1 bin]$ srvctl stop listener -n node1

[grid@node1 bin]$ srvctl status listener -n node1

Listener LISTENER is enabled on node(s): node1

Listener LISTENER is not running on node(s): node1

2.  Shutdown RAC Database Instances on all nodes:

 

Suppose DBA has two node RAC database, So he has to stop all instances from all DB nodes. Here, I am taking an example of two node RAC. First, I am checking on which server database is running and then stopping and verify for the same.

 

Syntax: srvctl stop database -d {databasename}

[oracle@node2 ~]$ srvctl status database -d oradb

Instance oradb1 is running on node node1

Instance oradb2 is running on node node2

[oracle@node2 ~]$ srvctl stop database -d oradb

[oracle@node2 ~]$ srvctl status database -d oradb

Instance oradb1 is not running on node node1

Instance oradb2 is not running on node node2

We just need to execute one command from any one of the server having database and it will stop all database instances on all servers. If you have more than one database configured on Nodes, then Database Administrator has to execute this command for each database.

3.  Shutdown All ASM instances from all nodes:

 

Next DBA has to shut down an ASM instance which are used to acess database, enter the following command, where node is the

name of the node where the ASM instance is running.

Syntax: srvctl stop asm -n {node}

 

[grid@node2 oracle]# srvctl stop asm -n node1 -f

 

[grid@node2 oracle]# srvctl stop asm -n node2 -f

 

[grid@node2 oracle]# srvctl status asm -n node1

 ASM is not running on node1

[grid@node2 oracle]# srvctl status asm -n node2

ASM is not running on node2

Sometimes, Database administrator 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:

 

To stop node applications running on a node, enter the following command, where node is the name of the node where the applications are running

 

[grid@node2 oracle]# srvctl stop nodeapps -n node1 -f

 

[grid@node2 oracle]# srvctl status nodeapps -n node1

 

VIP node1-vip is enabled

VIP node1-vip is running on node: node1

Network is enabled

Network is running on node: node1

GSD is disabled

GSD is not running on node: node1

ONS is enabled

ONS daemon is running on node: node1

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.

 

 

5.  Shut down the Oracle Clusterware or CRS:

 

In this command all CRS related process will be stopped. This is the only command which needs to be executed by "root" user on all database 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

*********************************************

 [root@node1 bin]# crsctl stop crs

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'node1'

CRS-2673: Attempting to stop 'ora.crsd' on 'node1'

CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'node1'

CRS-2673: Attempting to stop 'ora.LISTENER_SCAN2.lsnr' on 'node1'

CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'node1'

CRS-2673: Attempting to stop 'ora.LISTENER_SCAN3.lsnr' on 'node1'

CRS-2673: Attempting to stop 'ora.node2.vip' on 'node1'

-------------------------------------------------

-------------------------------------------------

-------------------------------------------------

CRS-2677: Stop of 'ora.cssd' on 'node1' succeeded

CRS-2673: Attempting to stop 'ora.gipcd' on 'node1'

CRS-2677: Stop of 'ora.gipcd' on 'node1' succeeded

CRS-2673: Attempting to stop 'ora.gpnpd' on 'node1'

CRS-2677: Stop of 'ora.gpnpd' on 'node1' succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'node1' has completed

CRS-4133: Oracle High Availability Services has been stopped.

[root@node1 bin]# crsctl check cluster –all

CRS-4639: Could not contact Oracle High Availability Services

CRS-4000: Command Check failed, or completed with errors.

DBA can see Now RAC is completely down. Now you can move ahead with your patching, maintenance activity.  Next let's see how to start Oracle RAC cluster database.