E How to Stop Processes in an Existing Oracle Real Application Clusters Database

This appendix describes how to stop all processes in an Oracle Real Application Clusters (Oracle RAC) database, in preparation for adding additional products to an existing database, or in preparation for patch updates.

This appendix contains the following topics:

Back Up the Oracle RAC Database
Shut Down Oracle RAC Databases
Stop All Oracle Processes

E.1 Back Up the Oracle RAC Database

Before you make any changes to the Oracle software, Oracle recommends that you create a backup of the Oracle Database installation.

E.2 Shut Down Oracle RAC Databases

Shut down any existing Oracle Database instances on each node, with normal or immediate priority. You can use Enterprise Manager or SRVCTL to shut down the Oracle RAC databases and their instances.

Note:

If you are using Oracle Clusterware or Oracle Restart, then you must shut down all Oracle Database instances on all cluster nodes before modifying the Oracle software. If you are performing a patch update, then review the instructions in the Patch Set Notes for detailed instructions.

E.3 Stop All Oracle Processes

Stop all listener and other processes running in the Oracle home directories where you want to modify the database software.

Note:

Before you can shut down Oracle ASM instances, Oracle Clusterware, or Oracle Restart, you must first shut down all database instances that use them.

This section contains the following topics:

Stopping Oracle Database Processes Before Adding Products or Upgrading
Stopping Oracle Clusterware or Cluster Ready Services Processes

E.3.1 Stopping Oracle Database Processes Before Adding Products or Upgrading

This section provides an overview of what needs to be done before adding additional products to Oracle Database 11g release 2 (11.2). If you are performing a patch upgrade, then refer to the Database Patch Set Notes for the patch for additional instructions.

Note:

You must perform these steps in the order listed.

Shut down any processes in the Oracle home on each node that can access a database.

Note:
Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime, rather than an unplanned system outage.

For example:
```
C:\> Oracle_home\bin\emctl stop dbconsole
```
Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database:
```
C:\> Oracle_home\bin\srvctl stop database -d db_name
```

E.3.2 Stopping Oracle Clusterware or Cluster Ready Services Processes

If you are modifying an Oracle Clusterware or Oracle ASM installation, then shut down the following Oracle Database services.

Note:

You must perform these steps in the order listed.

Shut down any processes in the Oracle home on each node that might be accessing a database; for example, Oracle Enterprise Manager Database Control.

Note:
Before you shut down any processes that are monitored by Oracle Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime, rather than an unplanned system outage.
Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database:
```
Oracle_home\bin\srvctl stop database -d db_name
```
Stop all node applications on all nodes. To stop node applications running on a node, enter the following command, where C:\app\grid\11.2.0 is the grid infrastructure home, and node is the name of the node where the applications are running
```
C:\> app\grid\11.2.0\bin\srvctl stop nodeapps -n node
```
Shut down the Oracle Clusterware (or CRS processes) and Oracle ASM instance by entering the following command on all nodes as a user with Administrator privileges.
```
C:\app\...\bin> crsctl stop cluster
```
If you want to stop Oracle Clusterware and Oracle ASM instances on all nodes in the cluster, then you can enter a single command: crsctl stop cluster -all.

Note:
The crsctl stop crs command is used to stop Oracle High Availability services for single-instance databases.
Shut down the Oracle Clusterware or CRS processes from the Services window.

Access the Services window by clicking Start, selecting Control Panel, selecting Administrative Tools, and then selecting Services. In the Services window, shut down the following services:
- Oracle Object Service
- OracleClusterVolumeService
- OracleOHService
  
  Note:
  Depending on your configuration, your nodes might not be running all of the services listed.