| Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g Release 2 (10.2) for Microsoft Windows Part Number B14207-04 |
|
|
View PDF |
| Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g Release 2 (10.2) for Microsoft Windows Part Number B14207-04 |
|
|
View PDF |
This appendix describes how to stop all processes in an Oracle Real Application Clusters (RAC) database, in preparation for adding additional products to an existing database, or in preparation for patch updates. The topics in this appendix are:
Before you make any changes to the Oracle software, Oracle recommends that you create a backup of your current installation.
Shut down any existing Oracle Database instances on each node, with normal or immediate priority.If Automatic Storage Management (ASM) is running, shut down all databases that use ASM, and then shut down the ASM instance on each node of the cluster.
|
Note: If you are using Oracle Clusterware or Cluster Ready Services, 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, review the instructions in the Patch Set Notes for detailed instructions. |
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. |
If you stopping the processes to install a patch that supports rolling upgrades, then complete the following steps on the node where you will run the installer to perform the upgrade. To stop Oracle Clusterware and Cluster Ready Services on all of the nodes a non-rolling upgrade or for some other reason, perform these steps on each node:
|
Note: If you are stopping the processes on more than one node, then you must complete all of these steps, in the order listed, on one node before you perform any of these steps on another node. |
Shut down any processes in the Oracle home that might be accessing a database; for example, 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 RAC instances on the node. To shut down all 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. 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. 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
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, then selecting Services. From the Services window, shut down the following services:
|
Note: Depending on your configuration, your nodes may not be running all of the services listed. |
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.
If node applications are running in the RAC Oracle home, then shut down the following Oracle Database 10g services before modifying the Oracle Database software:
|
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, 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 RAC instances on all nodes. To shut down all 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
