Preface

This gu ide provides a basic conceptual overview of Oracle database backup and recovery.

This prefac e contains these topics:

Audience< /a>

Audience

This manual is intended for database administrators who perform backup and recovery of an Oracle database server.

To use this document, you need to know the following:

Relational database concepts and basic database administration as described i n Oracle Database Concepts and Oracle Database Administrator's Guide
The operating system environment under which you are running the Oracle database

Organization

This document contains:

Chapter 1, "Backup and Recovery Overview"

This chapter briefly i ntroduces the basic concepts of Oracle database backup and recovery.

Chapter 2, "Backup and Recovery Strategies"

This chapter gives general recommendations for a backup and recovery strategy.

Chapter 3, "Setting Up and Configuring Backup and R ecovery"

This chapter describes how to prepare RMAN for initial use.

Chapter 4, "Making Backups with Recovery Manager"

This chapter describes how to use the RMAN BACKUP command.


 
Chapt
er 5, "Performing Recovery"

This chapter describes how to use the RMAN RESTORE and RECOVER commands.

Chapter 6, "Recovery Manager Maintenance Tasks"

This chapter describes how to maintain the RMAN backup metadata, which is stored in the control file of the target database.

"Glossary"

This chapter defines common backup and recovery terms.

Conventions

This section describes the conventions used in the text an d 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 indic ates terms that are defined in the text or terms that appear in a glossary, or both.	< /a> When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle 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 el ements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or util ity 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. < /p> 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, direct ory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect ident ifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program un its, 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 `orapw d` file. Back up the datafiles and control files in the `/disk1/oracle/dbs` directory. The `department_id`, `department_name`, and `location_i d` columns are in the `hr.departments` table. Set the `QUERY_REWRITE_EN ABLED` initialization parameter to `true.` Connect as `oe` user. The `JRepUtil` class implements these methods.
`lowercase italic monospace (fixed-widt h) font`	Lowercase italic monospace font represents pla ceholders or variables.	You can specify the `parallel_cla use`. Run `U``old_release``.SQL` where < em>`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 (fixe d-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.

< td class="Informal">

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

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. D o not enter the braces.	{ENABLE \| DISABLE}
\|	A vertical bar represents a choice of two or more options within brackets or braces. Ente r one of the options. Do not enter the vertical bar.	{ENABLE \| D ISABLE} [COMPRESS \| NOCOMPRESS]
...	Horizontal el lipsis points indicate either: That we have omitted parts of th e code that are not directly related to the example That you can repeat a porti on of the code	CREATE TABLE ... AS < em class="Italic">subquery; SELECT col1, c ol2, ... , coln FROM employees;
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.	SQL> SELECT NAME FROM V$DATAFILE; NAME ------------------------------------ /fsl/dbs/tbs_01.dbf /fs1/dbs/tbs_02.dbf . . . /fsl/dbs/tbs_ 09.dbf 9 rows selected.
< a name="969451"> Other notation	You must enter s ymbols other than brackets, braces, vertical bars, and ellipsis points as shown.	acctbal NUMBER(11,2); acct CONSTANT NUMBER(4) := 3;
Italics	CONNECT SYSTEM/system_pas sword DB_NAME = database_name
UPPERCASE	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to disti nguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, bec ause these terms are not case sensitive, you can enter them in lowercase.	SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TA BLE 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 sh own.	SELECT last_name, employee_id FROM employees; sqlplus hr/hr CREATE USER mjones IDENTIFIED BY ty3MU9;

Documentation Accessibility

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

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

Acce ssibility of Code Examples in Documentation

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

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizatio ns that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these W eb sites.