F How to Stop Processes in an Existing Oracle Real Application Clusters Database, and How to Perform Oracle Clusterware Rolling Upgrades

This appendix describes how to stop processes in an Oracle Real Application Clusters (RAC) database, for one of the following two scenarios:

Scenario One: Stopping processes in an entire database, in preparation for adding additional products to an existing database, or in preparation for patch updates.

Scenario Two: Stopping processes on selected nodes in a database, in preparation for performing a rolling upgrade of Oracle Clusterware from any 10.2 installation to the latest patch set update; for example, you can perform a rolling upgrade from 10.2.0.1 to 10.2.0.3.

This appendix contains the following topics:

Back Up the Oracle Software
Verify System Readiness for Patches and Upgrades
How to Stop Processes in an Existing Oracle Database
How to Perform Oracle Clusterware Rolling Upgrades

F.1 Back Up the Oracle Software

Before you make any changes to the Oracle software, whether you intend to upgrade or patch part of the database or clusterware, or all of your cluster installation, Oracle recommends that you create a backup of the Oracle software.

F.2 Verify System Readiness for Patches and Upgrades

If you are completing a patch update of your database or clusterware, then after you download the patch software, and before you start to patch or upgrade your database, review the Patch Set Release Notes that accompany the patch to determine if your system meets the system requirements for the operating system and the hardware platform.

Use the Cluster Verification Utility to assist you with system checks in preparation for starting a database patch or upgrade.

F.3 How to Stop Processes in an Existing Oracle Database

To stop process in an existing Oracle Real Application Clusters Database, where you want to shut down the entire database, complete the following steps.

F.3.1 Shut Down Oracle Real Application Clusters Databases

Shut down any existing Oracle Database instances on each node, with normal or immediate priority.If Automatic Storage Management (ASM) is running, then shut down all databases that use ASM, and then shut down the ASM instance on each node of the cluster.

Note:

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

F.3.2 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:

If you shut down ASM instances, then you must first shut down all database instances that use ASM, even if these databases run from different Oracle homes.

F.3.2.1 Stop Oracle Clusterware or Cluster Ready Services Processes

If you are modifying an Oracle Clusterware or Oracle Cluster Ready Services (CRS) installation, then shut down the following Oracle Database 10g 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, shut down Oracle Enterprise Manager Database Control.

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.
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
```
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
```
$ oracle_home/bin/srvctl stop asm -n node
```
Stop all node applications on all 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
```
$ oracle_home/bin/srvctl stop nodeapps -n node
```
Log in as the root user, and shut down the Oracle Clusterware or CRS process by entering the following command on all nodes:
```
# CRS_home/bin/crsctl stop crs
```

F.3.2.2 Stop Oracle Database 10g Processes Before Adding Products or Upgrading

This section provides an overview of what needs to be done before adding additional products to Oracle Database 10g Release 2 (10.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; for example, shut down Oracle Enterprise Manager Database Control.

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.
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
```
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
```
$ oracle_home/bin/srvctl stop asm -n node
```

F.4 How to Perform Oracle Clusterware Rolling Upgrades

To perform a rolling upgrade, complete all of the following steps in sequence.

Copy Patch Software to the Primary Upgrade Node
Shut Down Oracle Real Application Clusters Instances on Upgrade Nodes
Stop All Oracle Processes on Upgrade Nodes
Start OUI and Complete Upgrade Processes on Upgrade Nodes

Note:

To perform rolling upgrades, the existing Oracle Clusterware home directory, commonly referred to in Oracle documentation as CRS home, must be located on local directories on the node. You cannot perform rolling upgrades on a shared CRS home directory.

F.4.1 Copy Patch Software to the Primary Upgrade Node

Download the patch software to the primary node on the cluster (the node where you performed initial Oracle Clusterware and Oracle Database installation). Review the patch set Readme to confirm that your system meets the system requirements for the patch set updates, and complete any special instructions for particular environments or configurations.

To download patches, or download the patch note Readme:

Log in to OracleMetaLink (https://metalink.oracle.com)
Click the Patches & Updates tab.
Search for the patch that you want to install.
Click the patch number to open the patch page

From this location, you can download the patch binary, download the patch Readme, and obtain other information regarding the patch update.
Download the patch set installation archive to a directory inside the Oracle base directory that meets the following requirements:
- It is not the exiting Oracle home directory, or CRS home directory
- It is not under an existing Oracle home directory, or CRS home directory
Extract the patch set installation archive

F.4.2 Shut Down Oracle Real Application Clusters Instances on Upgrade Nodes

On each node on which you want to perform a rolling upgrade, shut down the Oracle Database instance, with normal or immediate priority. If Automatic Storage Management (ASM) is running, then for each node that you intend to perform a rolling upgrade, shut down the database that uses ASM, and then shut down the ASM instance on the node.

Note:

To upgrade Oracle Clusterware or Cluster Ready Services, you must shut down all Oracle Database instances on all cluster nodes that you intend to upgrade before modifying the Oracle software. If you are performing a patch update, review the instructions in the Patch Set Notes for detailed instructions.

F.4.3 Stop All Oracle Processes on Upgrade Nodes

On each node on which you want to perform a rolling upgrade, before you upgrade Oracle Clusterware or Oracle Cluster Ready Services installations, you must shut down Oracle Database services that use clusterware processes.

Complete the following steps:

Note:

You must perform these steps in the order listed.

Shut down any processes on each node you intend to upgrade that might be accessing a database, such as Oracle Enterprise Manager Database Control.

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.
Shut down all Oracle RAC instances on each node you intend to upgrade. To shut down Oracle RAC instances on individual nodes in the database, enter the following command, where db_name is the name of the database, and instance_name is the name of the instance:
```
$ oracle_home/bin/srvctl stop instance -d db_name -i instnce_name
```
Repeat this process on each node of the cluster on which you intend to perform the rolling upgrade.
Shut down ASM instances on each node on which you intend to perform the rolling upgrade.

Note:
If you shut down ASM instances, then you must first shut down all database instances on the nodes you intend to upgrade that use ASM, even if these databases run from different Oracle homes.

To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
```
$ oracle_home/bin/srvctl stop asm -n node
```
Stop all node applications on each node on which you intend to perform the rolling upgrade. 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
```
$ oracle_home/bin/srvctl stop nodeapps -n node
```
On each node where you intend to perform the rolling upgrade, shut down the Oracle Clusterware or CRS process by entering the following command as the root user:
```
# CRS_home/bin/crsctl stop crs
```

F.4.4 Start OUI and Complete Upgrade Processes on Upgrade Nodes

To complete the patch upgrade, use the Oracle Universal Installer (OUI) downloaded with the patch update.

Complete the following steps:

Start the patch set OUI. At the Welcome window, click Next.
On the Specify Home Details window, select the CRS home directory, and click Next.
On the Specify Hardware Cluster Installation Nodes window, select the nodes where you want to perform the upgrade, and click Next.
Follow further instructions as directed from the OUI windows.
At the end of the install, OUI instructs you to run the command to stop Oracle Clusterware.

Open a terminal window, log in as the root user, and enter a command similar to the following on the first node to stop the CRS daemons in the existing Oracle home:
```
# CRS_home/bin/crsctl stop crs
```
When you are prompted by OUI, from the terminal window you opened in the previous step, enter a command similar to the following:
```
# CRS_home/install/root102.sh
```
When the install script completes, it displays text similar to the following, where patch_version displays the patch version you are installing:
```
patch_version patch successfully applied.
clscfg -upgrade completed successfully
```
This indicates that the upgrade process is complete. The upgraded Oracle Clusterware stack and AUTOSTART resources are started on the node.

Repeat steps 4 and 5 for each node on which you are performing a rolling upgrade.