Preface

This guide describes the administration of Oracle Real Application Clusters Guard. It describes the configuration parameters, how to set up customized features, how to use the command line interface, how to set up the network configuration, and how to troubleshoot Oracle Real Application Clusters Guard.

Audience

This document is intended for database administrators and system administrators who need to administer an Oracle Real Application Clusters Guard environment. They are assumed to have a thorough understanding of the concepts of Oracle Real Application Clusters Guard, the administration of the Oracle server and Oracle9i Real Application Clusters, and their platform-specific cluster technology.

Organization

This chapter describes the configuration parameters for Oracle Real Application Clusters Guard and discusses their values. It also explains how to change their values.

Chapter 2, "Using Oracle Real Application Cluster Guard Commands"

This chapter explains how to use the command line interface of Oracle Real Application Clusters Guard.

Chapter 3, "Customizing Oracle Real Application Clusters Guard"

This chapter describes how to customize the call-home feature, the custom query, role change notification, and Oracle Enterprise Manager for Oracle Real Application Clusters Guard. It also explains how to use the DBMS_LIBCACHE package to warm the cache on the secondary instance.

Chapter 4, "Administering Oracle Real Application Clusters Guard"

This chapter describes how to administer planned outages, recover from unplanned outages, and administer application failover, backups, and configuration changes.

Lowercase monospace typeface indicates sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, user names and roles, program units, and parameter values.

The deptno, dname, and loc columns are in the scott.dept table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Connect to the sales@sf.acme.com database.

Connect as oe user.

Conventions in Code Examples

Code examples illustrate RMAN, SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a fixed-width font and separated from normal text as shown in this example:

BACKUP DATABASE;

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention

Meaning

Example

[ ]

Brackets enclose one or more optional items. Do not enter the brackets.

DECIMAL (digits [ , precision ])

{ }

Braces enclose two or more items, one of which is required. Do not enter the braces.

{ENABLE | DISABLE}

|

A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.

{ENABLE | DISABLE}

[COMPRESS | NOCOMPRESS]

...

Horizontal ellipsis points indicate either:

That we have omitted parts of the code that are not directly related to the example

That you can repeat a portion of the code

CREATE TABLE ... AS subquery;

SELECT col1, col2, ... , coln FROM emp;

.

.

.

Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.

Other punctuation

You must enter punctuation other than brackets, braces, vertical bars, and ellipsis points as it is shown.

Italics

Italicized text indicates variables for which you must supply particular values.

STARTUP PFILE=initsid.ora

In this example, the entire string initsid.ora is a placeholder for a parameter file that must contain your particular instance ID or SID.

UPPERCASE

Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.

Documentation Accessibility

Oracle's goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.