Preface

Oracle9i Real Application Clusters Administration explains the Real Application Clusters-specific administrative tasks that supplement single instance administrative tasks. Information in this manual applies to Real Application Clusters as it runs on all operating systems. Where necessary, this manual refers to platform-specific documentation.

Real Application Clusters is a new breakthrough architecture with scalability and high availability features that exceed the capabilities of previous Oracle cluster-enabled software releases.

See Also:

The Oracle9i Real Application Clusters Documentation Online Roadmap to help you use the online Real Application Clusters Documentation set

This preface contains these topics:

Audience

Oracle9i Real Application Clusters Administration is written primarily for network or Database Administrator (DBA) responsible for the administration of Real Application Clusters.

To use this document you should first read the Oracle9i Database Administrator's Guide to become familiar with single-instance administrative procedures. You should then read Oracle9i Real Application Clusters Concepts for a conceptual understanding of Real Application Clusters processing. You should also have installed Real Application Clusters using the document Oracle9i Real Application Clusters Installation and Configuration and any platform-specific documentation.

Organization

This document contains the following five parts:

Part I: "Introduction to Administering Real Application Clusters"

Part One describes Real Application Clusters administration and your initial administrative tasks.

Chapter 1, "Introduction to Real Application Clusters Administration"

This chapter introduces the administrative tasks for Real Application Clusters software.

Chapter 2, "Parameter Management in Real Application Clusters Environments"

This chapter describes parameter files and Real Application Clusters-specific parameters.

Chapter 3, "Administering Storage Components in Real Application Clusters"

This chapter explains how to administer storage components in Real Application Clusters.

Chapter 4, "Administering Real Application Clusters Databases with Server Control, SQL, and SQL*Plus"

This chapter explains how to administer Real Application Clusters databases with Server Control, SQL, and SQL*Plus.

Part II: Using Oracle Enterprise Manager to Administer Real Application Clusters

Part Two describes how to use Oracle Enterprise Manager to administer Real Application Clusters databases.

Chapter 5, "Administering Real Application Clusters Databases with Oracle Enterprise Manager"

This chapter describes how to use Oracle Enterprise Manager to administer Real Application Clusters databases.

Part III: Backup and Recovery in Real Application Clusters

Part Three provides backup and recovery procedures for Real Application Clusters.

Chapter 6, "Configuring RMAN for Real Application Clusters"

This chapter describes how to configure RMAN for Real Application Clusters.

Chapter 7, "Backing Up Real Application Clusters Databases"

This chapter explains how to backup Real Application Clusters databases.

Chapter 8, "Database Recovery in Real Application Clusters"

This chapter explains database recovery in Real Application Clusters databases.

Part IV: Scaling Your Real Application Clusters Environment

Part Four provides information about adding nodes and instances to scale your Real Application Clusters environment.

Chapter 9, "Adding Nodes and Instances and Deleting Instances in Real Application Clusters"

This chapter explains how to add nodes and instances and how to delete instances in Real Application Clusters using the Oracle Universal Installer and the Oracle Database Configuration Assistant.

Part V: Reference

Part Five provides reference information for Real Application Clusters.

Appendix A, "Troubleshooting"

This chapter describes how to use trace files for troubleshooting Oracle installation issues. It also explains how to contact Oracle Customer Support.

Glossary

The glossary defines terms used in this book as well as terms relevant to the subject matter of this book.

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle9i Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
`UPPERCASE monospace (fixed-width font)`	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	You can specify this clause only for a `NUMBER` column. You can back up the database by using the `BACKUP` command. Query the `TABLE_NAME` column in the `USER_TABLES` data dictionary view. Use the `DBMS_STATS`.`GENERATE_STATS` procedure.
`lowercase monospace (fixed-width font)`	Lowercase monospace typeface indicates executables, filenames, directory names, and 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, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	Enter `sqlplus` to open SQL*Plus. The password is specified in the `orapwd` file. Back up the data files and control files in the `/disk1/oracle/dbs` directory. The `department_id`, `department_name`, and `location_id` columns are in the `hr.departments` table. Set the `QUERY_REWRITE_ENABLED` initialization parameter to `true.` Connect as `oe` user. The `JRepUtil` class implements these methods.
`lowercase monospace (fixed-width font) italic`	Lowercase monospace italic font represents placeholders or variables.	You can specify the `parallel_clause`. Run `U``old_release``.SQL` where `old_release` refers to the release you installed prior to upgrading.

Conventions in Code Examples

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

SELECT username FROM dba_users WHERE username = 'MIGRATE';

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 employees;`
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.
Other notation	You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.	`acctbal NUMBER(11,2);` `acct CONSTANT NUMBER(4) := 3;`
`Italics`	Italicized text indicates placeholders or variables for which you must supply particular values.	`CONNECT SYSTEM/``system_password` `DB_NAME =` `database_name`
`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.	`SELECT last_name, employee_id FROM employees;` `SELECT * FROM USER_TABLES;` `DROP TABLE hr.employees;`
`lowercase`	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	`SELECT last_name, employee_id FROM employees;` `sqlplus hr/hr` `CREATE USER mjones IDENTIFIED BY ty3MU9;`

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:

http://www.oracle.com/accessibility/

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.