Skip Headers
Oracle® Real Application Clusters Installation Guide
11g Release 1 (11.1) for Linux and UNIX

B28264-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

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:

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.

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:

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, 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:

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.

This section contains the following topics:

E.3.1 Stopping 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 services.

Note:

You must perform these steps in the order listed.
  1. 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.
  2. 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
    
  3. 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
    
  4. 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
    
  5. Shut down the Oracle Clusterware or CRS process by entering the following command on all nodes as the root user

    # /etc/init.d/init.crs stop
    

E.3.2 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 1 (11.1). 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 Oracle RAC Oracle home, then shut down the following Oracle Database services before modifying the Oracle Database software:

Note:

You must perform these steps in the order listed.
  1. 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:

    $ORACLE_HOME/bin/emctl stop dbconsole
    $ORACLE_HOME/bin/searchctl stop
    
  2. 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
    
  3. 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
    
  4. 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