Skip Headers
Oracle® Real Application Clusters Installation Guide
12c Release 1 (12.1) for Linux and UNIX

E17889-12
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

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

D.1 Backing 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.

D.2 Shutting Down Oracle RAC Databases

Shut down any existing Oracle Database instances on each node, with normal or immediate priority. You can use Oracle Enterprise Manager or the Server Control (SRVCTL) utility 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.

See Also:

Oracle Database Administrator's Guide for more information about Oracle Restart

D.3 Stopping 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.

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

This section provides an overview of what must be done before adding additional products to Oracle Database 12c Release 1 (12.1). If you are updating only the Oracle Database software, then you only need to stop the databases instances that run from the Oracle home being updated. 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.
  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 Oracle Enterprise Manager Cloud Control, set a blackout in Oracle Enterprise Manager Cloud 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 -db db_name
    

See Also:

D.3.2 Stopping Oracle Clusterware and Oracle ASM Instances

If you are upgrading the Oracle Clusterware or Oracle ASM software, then you must first stop all Oracle RAC database instances and all Oracle database instances that use Oracle ASM for storage. After stopping the database instances, shut down the Oracle ASM instances and Oracle Clusterware, as described in the following steps:

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, the Oracle Enterprise Manager Cloud Control agent or an Oracle Net Services listener.

    Note:

    Before you shut down any processes that are monitored by Oracle Enterprise Manager Cloud Control, set a blackout in Oracle Enterprise Manager Cloud 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 -db db_name
    
  3. Stop all Oracle Clusterware node applications node applications and resources on all nodes. To stop node applications running on a node, enter the following command, where u01/app/grid/12.1.0 is the Grid home, and node is the name of the node where the applications run:

    $ u01/app/grid/12.1.0/bin/srvctl stop nodeapps -node node
    
  4. Shut down the Oracle Clusterware processes and the Oracle ASM instance on each node by entering the following command on all nodes as the root user:

    # crsctl stop cluster
    

    To stop Oracle Clusterware and Oracle ASM instances on all nodes in the cluster, you can enter a single command: crsctl stop cluster -all.

    Note:

    The crsctl stop crs command is used to stop Oracle Restart services for single-instance databases.

D.4 Using CVU to Validate Readiness for Oracle RAC Upgrades

Review the contents in this section to validate that your Oracle RAC cluster is ready for upgrades.

D.4.1 About the CVU Database Upgrade Validation Command Options

Use the Cluster Verification Utility (CVU) command cluvfy stage -predbinst -upgrade to check the readiness of your Oracle RAC installation for upgrades. Running cluvfy with the -predbinst -upgrade flags performs system checks to confirm if the cluster is in a correct state for upgrading from an existing Oracle RAC installation.

The command uses the following syntax, where variable content is indicated by italics:

cluvfy stage -pre dbinst -upgrade -src_dbhome src_RAChome  -dest_dbhome 
dest_RAChome -dest_version dest_version [-fixup[-fixupdirpath]] [-verbose]

The options are:

  • -src_dbhome src_RAChome

    Use this flag to indicate the location of the source Oracle RAC home that you are upgrading, where src_RAChome is the path to the home to upgrade.

  • -dest_dbhome dest_RAChome

    Use this flag to indicate the location of the upgrade Oracle RAC home, where dest_RAChome is the path to the Oracle RAC home.

  • -dest_version dest_version

    Use this flag to indicate the release number of the upgrade, including any patchset. The release number must include the five digits designating the release to the level of the platform-specific patch. For example: 12.1.0.1.0.

    See Also:

    Oracle Database Administrator's Guide for information about release number format
  • -fixup [-fixupdir fixupdirpath]]

    Use the -fixup flag to indicate that you want to generate instructions for any required steps you must complete to ensure that your cluster is ready for an upgrade. The default location is the CVU work directory. To place the fixup instructions in a different directory, add the flag -fixupdir, and provide the path to the fixup directory.

  • -verbose

    Use the -verbose flag to produce detailed output of individual checks.

D.4.2 Example of Verifying System Upgrade Readiness for Oracle RAC Infrastructure

You can verify that the permissions required for installing Oracle RAC have been configured on the nodes node1 and node2 by running the following command:

$ ./cluvfy stage -pre dbinst -upgrade -src_dbhome /u01/app/oracle/product/11.2.0/dbhome_1 -dest_dbhome 
/u01/app/oracle/product/12.1.0/dbhome_1 -dest_version 12.1.0.0.0 -fixup
-fixupdirpath /home/oracle/fixup -verbose

D.4.3 Verifying System Readiness for Oracle Database Upgrades

Use Cluster Verification Utility (CVU) to assist you with system checks in preparation for starting a database upgrade. The installer runs the appropriate CVU checks automatically, and either prompts you to fix problems, or provides a fixup script to be run on all nodes in the cluster before proceeding with the upgrade.