Oracle8i Backup and Recovery Guide Release 8.1.5 A67773-01 |
|
Part / Chapter | Contents | |
---|---|---|
PART 1 |
Developing a Backup and Recovery Strategy |
|
Offers a general overview of backup and recovery concepts and methods. |
||
Describes how to manage control files, online redo logs, and archived redo logs for backup and recovery. |
||
Provides guidelines for developing a backup and recovery strategy. |
||
PART 2 |
Using Recovery Manager |
|
Describes the features and functionality of the Recovery Manager utility. |
||
Describes how to start using Recovery Manager, including whether you should use a recovery catalog, how you can execute commands, and how to connect to a target database. |
||
Describes how to manage RMAN metadata using either a recovery catalog or the control file. |
||
Chapter 7, "Generating Lists and Reports with Recovery Manager" |
Describes how to generate lists of your backups and copies and reports describing which datafiles need to be backed up, which backups are obsolete, and the structure of the database schema at a specified time. |
|
Chapter 8, "Making Backups and Copies with Recovery Manager" |
Describes how to make backup and image copies of datafiles, control files, and archived redo logs using Recovery Manager. |
|
Describes how to restore backups and copies of datafiles, control files, and archived redo logs and perform media recovery on datafiles. |
||
Chapter 10, "Creating a Duplicate Database with Recovery Manager" |
Describes how to create a duplicate of your target database on either a local or remote host using backups of your target database datafiles. |
|
PART 3 |
Recovery Manager Reference |
|
Provides syntax diagrams, parameter descriptions, and code samples for all RMAN commands. |
||
Describes the views available with a recovery catalog. |
||
PART 4 |
Using O/S Commands for Backup and Recovery |
|
Provides step-by-step instructions for performing operating system backups. |
||
Provides step-by-step instructions for performing media recovery using operating system commands. |
||
Describes the procedures for performing media recovery in several common scenarios. |
||
Explains how to plan, create, and maintain a standby database. |
||
Appendix A, "Performing Tablespace Point-in-Time Recovery with Recovery Manager" |
Provides planning guidelines and step-by-step instructions for performing tablespace point-in-time recovery with Recovery Manager. |
|
Appendix B, "Performing Operating System Tablespace Point-in-Time Recovery" |
Provides planning guidelines and step-by-step instructions for manually performing tablespace point-in-time recovery. |
This guide is for DBAs who administer the backup, restore, and recovery operations of an Oracle database system.
Readers of this guide are assumed to be familiar with relational database concepts and basic database administration. They are also assumed to be familiar with the operating system environment under which they are running Oracle.
This section explains the conventions used in this manual including the following:
This section explains the conventions used within the text:
Uppercase text is used to call attention to tablespace names, initialization parameters, and SQL keywords.
For example, "If you create a private rollback segment, the name must be included in the ROLLBACK_SEGMENTS parameter of the init.ora
file. You can view this information by issuing a SHOW PARAMETER statement in SQL*Plus."
Italicized words within text are book titles, new vocabulary, emphasized words, or variables in SQL or Recovery Manager syntax.
For example, "An archived redo log is an online redo log that has been copied offline. You must run your database in ARCHIVELOG mode to enable this feature. If you are using Recovery Manager, you can specify an archived redo log in a backup command by using the archivelog like '/oracle/archive/arc_*' sub-clause."
Bold words within text are Recovery Manager keywords or operating system-specific commands.
For example, "Use the Recovery Manager backup command to back up your database. Alternatively, use the UNIX cp command to copy files."
Monospaced
CharactersFilenames and directories appear in a monospaced font. Also, monospaced characters in text preceding a code example indicates a filename or keyword used in the sample code.
For example, "This command backs up the tablespace TBS_1:
run { allocate channel c1 type disk; backup tablespace tbs_1; }
For information about Recovery Manager syntax conventions, see "Conventions Used in this Reference".
SQL, SQL*Plus, and Recovery Manager commands and statements appear separated from the text of paragraphs in a monospaced font. For example:
INSERT INTO emp (empno, ename) VALUES (1000, 'SMITH'); ALTER TABLESPACE users ADD DATAFILE 'users2.ora' SIZE 50K; run { allocate channel ch1 type disk; backup database; }
When you run RMAN from the command line, the command prompt appears as RMAN>
. When you issue commands from the SQL*Plus command line, the prompt appears as SQL>
. These prompts are displayed in the code examples only when they are necessary to prevent confusion.
You can execute SQL, SQL*Plus, and RMAN commands in different environments on different platforms. As much as possible, this guide attempts to provide generic documentation, that is, documentation that is not specific to any operating system or interface. Nevertheless, it is sometimes necessary for illustrative purposes to show how the syntax works at the O/S level. In these cases, this book uses examples from a UNIX command-line interface and employs the %
symbol to indicate the O/S prompt. For example:
% rman target / rcvcat rman/rman@inst2 RMAN> startup
Every reader of this guide is presumed to have read:
You will often need to refer to the following reference guides: