Skip Headers
Oracle® Database 2 Day + Real Application Clusters Guide
11g Release 2 (11.2)

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

Go to previous page
Go to next page
View PDF

1 Introduction to Oracle Database 2 Day + Real Application Clusters Guide

Oracle Real Application Clusters (Oracle RAC) enables a single database to run across a cluster of servers, providing fault tolerance, performance, and scalability with no application changes necessary. Oracle RAC provides high availability for applications by removing the single point of failure with a single server.

This chapter provides an overview of Oracle Real Application Clusters (Oracle RAC) environments. This chapter includes the following sections:

About This Guide

This is a task-oriented guide for Oracle Real Application Clusters (Oracle RAC) database administration. This guide shows you how to configure and manage the environment for Oracle Clusterware and Oracle RAC. This guide also explains how to create an Oracle RAC database and how to perform routine Oracle RAC database administrative tasks.

The goal of this guide is to help you understand the basic steps required to install and maintain an Oracle RAC environment, including how to perform basic troubleshooting, performance monitoring, and backup and recovery activities. This guide is based on Oracle Enterprise Linux, but you do not have to be a Linux expert to use this guide.

What This Guide Is Not

This guide is not a comprehensive description of Oracle RAC. It describes concepts only when necessary for completing a particular task.

Related Materials

This guide is part of a comprehensive set of learning materials for administering Oracle Databases, which includes a 2 Day DBA Oracle By Example (OBE) series (available on the Web) and Oracle University instructor-led classes. The Oracle By Example (OBE) series also has viewlets, or animated demos you can view using a Web browser.

You can view the Oracle By Example content for Oracle RAC at the following Web sites:

Overview of Oracle Real Application Clusters Documentation

This guide describes how to install, configure, and manage Oracle RAC, Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM). It provides examples for how you could deploy Oracle RAC on a two-node cluster, using the Oracle Enterprise Linux operating system. Oracle Enterprise Linux is fully compatible — both source and binary — with Red Hat Enterprise Linux. It includes the identical set of packages at the same version levels with the same source code as the Red Hat distribution.

This guide is for DBAs who have experience with single-instance Oracle environments and have read Oracle Database 2 Day DBA.

Useful Oracle RAC Guides

The following is a list of other useful Oracle RAC or related documentation:


Additional information for this release may be available in the Oracle Database 11g release 2 (11.2) README or Release Notes. You can locate these documents on your Oracle product installation media.

Other Useful Oracle Documentation

In addition to the Oracle Database 2 Day DBA guide, the following list displays other books in the Oracle documentation library that were referenced within this guide:


Additional information for this release may be available in the Oracle Database 11g release 2 (11.2) README or Release Notes. You can locate these documents on your Oracle product installation media.

About Oracle Grid Infrastructure for a Cluster and Oracle RAC

Starting with Oracle Database 11g Release 2, Oracle Clusterware and Oracle ASM are installed into a single home directory, which is called the Grid home. Oracle Grid Infrastructure for a cluster refers to the installation of the combined products. Oracle Clusterware and Oracle ASM are still individual products, and are referred to by those names.

Oracle Clusterware enables servers, referred to as hosts or nodes, to operate as if they are one server, commonly referred to as a cluster. Although the servers are standalone servers, each server has additional processes that communicate with other servers. In this way the separate servers appear as if they are one server to applications and end users. Oracle Clusterware provides the infrastructure necessary to run Oracle RAC. The combined processing power of the multiple servers provides greater availability, throughput, and scalability than is available from a single server.

The nodes in a cluster can be organized into a server pool for better resource management. Each server pool has the following properties:

Upon installation of Oracle Grid Infrastructure for a cluster, a default server pool, called the Free pool, is created automatically. All servers in a new installation are assigned to the Free server pool, initially. If you create a new server pool, the servers move from the Free pool to the new server pool automatically.

When you create an Oracle RAC database that is a policy-managed database, you specify the number of servers that are needed for the database, and a server pool is automatically created for the database. Oracle Clusterware populates the server pool with the servers it has available. If you do not use server pools, then you can create an administrator-managed database. For the purposes of this guide, we use an administrator-managed Oracle RAC database.

About Oracle Automatic Storage Management

With Oracle Real Application Clusters (Oracle RAC), each instance must have access to the data files and recovery files for the Oracle RAC database. Using Oracle Automatic Storage Management (Oracle ASM) is an easy way to satisfy this requirement.

Oracle ASM is an integrated, high-performance volume manager and file system. With Oracle Database 11g Release 2, Oracle ASM adds support for storing the Oracle Clusterware OCR and voting disk files, also a general purpose cluster file system called Oracle Automatic Storage Management Cluster File System (Oracle ACFS). Oracle ASM is based on the principle that the database should manage storage instead of requiring an administrator to do it. Oracle ASM eliminates the need for you to directly manage potentially thousands of Oracle database files.

Oracle ASM groups the disks in your storage system into one or more disk groups. You manage a small set of disk groups and Oracle ASM automates the placement of the database files within those disk groups. Oracle Cluster Registry (OCR) and voting disks can also be placed on Oracle ASM diskgroups.

In Figure 1-1, the normal redundancy disk group stored in Oracle ASM contains 3 failure groups (shown as 3 disks) to store the voting disk and OCR files for Oracle Clusterware. Because the voting disk records which nodes are currently members of the cluster, there must be at least 3 voting disks for a two-node cluster. If the Oracle ASM disk group did not contain the voting disk and OCR files, then you could have a normal redundancy disk group with only two failure groups.

Figure 1-1 Oracle Clusterware Files Stored in an Oracle ASM Disk Group

Description of Figure 1-1 follows
Description of "Figure 1-1 Oracle Clusterware Files Stored in an Oracle ASM Disk Group"

Oracle ASM provides the following benefits:

Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is a new multi-platform, scalable file system, and storage management technology that extends Oracle ASM functionality to support customer files maintained outside of the Oracle Database. Files supported by Oracle ACFS include database and application executables, trace files, alert logs, application reports, BFILEs, and configuration files. Oracle ACFS leverages Oracle ASM functionality to provide dynamic file system resizing, striping, and mirroring.

Oracle ASM is implemented as a special kind of Oracle instance, with its own System Global Area and background processes. The Oracle ASM instance is tightly integrated with Oracle Clusterware and Oracle Database. Every server running one or more database instances that use Oracle ASM for storage has an Oracle ASM instance. In an Oracle RAC environment, there is one Oracle ASM instance for each node, and the Oracle ASM instances communicate with each other on a peer-to-peer basis. Only one Oracle ASM instance is supported on a node, but you can have multiple database instances that use Oracle ASM residing on the same node. Figure 1-2, "Oracle Instances and Oracle ASM Storage" shows the storage configuration commonly used for a 2-node Oracle RAC database.

Figure 1-2 Oracle Instances and Oracle ASM Storage

Description of Figure 1-2 follows
Description of "Figure 1-2 Oracle Instances and Oracle ASM Storage"

Oracle recommends that you use Oracle ASM for your Oracle Clusterware files and Oracle RAC datafiles, instead of raw devices or the operating system file system. Oracle databases can use both Oracle ASM files and non-Oracle ASM files. You can also create an ACFS to store your database Oracle Home and any other external (non-database) files in the cluster.

About Oracle Real Application Clusters

Oracle RAC extends Oracle Database so that you can store, update, and efficiently retrieve data using multiple database instances on different servers at the same time. Oracle RAC provides the software that manages multiple servers as and instances as a single group. The data files that comprise the database must reside on shared storage that is accessible from all servers that are part of the cluster. Each server in the cluster runs the Oracle RAC software.

An Oracle Database database has a one-to-one relationship between data files and the instance. An Oracle RAC database, however, has a one-to-many relationship between data files and instances. In an Oracle RAC database, multiple instances access a single set of database files.

Each database instance in an Oracle RAC database uses its own memory structures and background processes. Oracle RAC uses Cache Fusion to synchronize the data stored in the buffer cache of each database instance. Cache Fusion moves current data blocks (which reside in memory) between database instances, rather than having one database instance write the data blocks to disk and requiring another database instance to reread the data blocks from disk. When a data block located in the buffer cache of one instance is required by another instance, Cache Fusion transfers the data block directly between the instances using the interconnect, enabling the Oracle RAC database to access and modify data as if the data resided in a single buffer cache.

Oracle RAC is also a key component for implementing the Oracle enterprise grid computing architecture. Having multiple database instances accessing a single set of data files prevents the server from being a single point of failure. If a node in the cluster fails, the Oracle Database continues running on the remaining nodes. Individual nodes can be shutdown for maintenance while application users continue to work.

Oracle RAC supports mainstream business applications, such as OLTP, DSS, and also popular packaged products such as SAP, PeopleSoft, Siebel, and Oracle E*Business Suite, as well as custom applications. Any packaged or custom application that scales on an Oracle Database scales well on Oracle RAC without requiring changes to the application code.

You will learn more about the operation of the Oracle RAC database in a cluster, how to build the cluster, and the structure of an Oracle RAC database in other sections of this guide.

About Oracle RAC One Node

Oracle RAC One Node databases are Oracle RAC databases that run in a cluster but usually run only one instance. Only when Oracle Clusterware detects an instance failure or during planned online database relocation operations is a second instance started so that the sessions can be migrated to a new node. After the migration, the original instance is shut down. This functionality is available starting with Oracle Database 11g Release 2 (

If you run your applications on Oracle RAC One Node, and your applications grow to the point that a single node cannot supply the resources they need, then Oracle RAC One Node can be upgraded online to Oracle Real Application Clusters. If the node running your Oracle RAC One Node database becomes overloaded, you can migrate the instance to another node in the cluster using online database relocation with no downtime for application users

About Installing Oracle RAC on Different Operating Systems

If you plan to install and configure Oracle RAC on an operating system other than Oracle Enterprise Linux, you can still use this guide to obtain a general understanding about how to deploy Oracle RAC. You can also use this guide for deploying Oracle RAC on clusters with more than two nodes. For all environments that do not match the environment that this guide describes, modify the examples accordingly.

When installing Oracle RAC on a different platform or different operating system version than Oracle Enterprise Linux or Red Hat Enterprise Linux, refer to the installation and configuration guides for that platform. For example, if you are installing Oracle RAC on the Solaris operating system, then you would use the following guides:

  • Oracle Grid Infrastructure Installation Guide for Solaris Operating System

  • Oracle Real Application Clusters Installation Guide for Solaris Operating System

Oracle Clusterware and Oracle RAC do not support heterogeneous platforms in the same cluster. For example, you cannot have one node in the cluster running Oracle Enterprise Linux and another node in the same cluster running Solaris UNIX. All nodes must run the same operating system, that is, they must be binary compatible. Oracle RAC does not support machines having different chip architectures in the same cluster. However, you can have machines of different speeds and sizes in the same cluster.

Tools for Installing, Configuring, and Managing Oracle RAC

The following is a description of the tools used for installing, configuring, and managing the Oracle Clusterware, Oracle Automatic Storage Management (Oracle ASM), and Oracle Real Application Clusters (Oracle RAC):

If you have installed Oracle Grid Infrastructure for a cluster for Oracle Database 11g release 2 (11.2), when using utilities to manage your cluster, databases, database instances, Oracle ASM, and listeners, use the appropriate binary that is in the home directory of the object or component you are managing and set your ORACLE_HOME environment variable to point to this directory. For example: