Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: reset database

Re: reset database

From: Peter Gram <peter.gram_at_miracleas.dk>
Date: Thu, 16 May 2002 02:09:07 -0800
Message-ID: <F001.004620FF.20020516020907@fatcity.com>






pls. next time read the manual. if the manual gives problem then describe the problem !

Oracle8i Recovery Manager User's Guide and Reference
Release 2 (8.1.6)

Part Number A76990-01

Library

Product

Contents

Index

Go to previous page Go to beginning of chapter Go to next page

Recovery Manager Command Syntax, 36 of 50


reset

Syntax


Purpose

To create a new database incarnation record in the recovery catalog. RMAN considers the new incarnation as the current incarnation of the database. All subsequent backups and redo log archiving operations performed by the target database will be associated with the new database incarnation.

Requirements

Keywords and Parameters

to incarnation primary_key 

changes the incarnation that RMAN considers to be current to an older incarnation. This option is useful in the rare circumstance in which you want to undo the effects of a RESETLOGS by restoring backups of a prior incarnation of the database.

Specify the primary key of the DBINC record for the database incarnation. Obtain the key value using the list incarnation of databasecommand. After you issue the reset database to incarnation command, issue restore and recover commands to restore the database files from the prior incarnation and recover them. 


Examples

Resetting a Database After RESETLOGS

The following example resets a database after performing incomplete media recovery:

run {  
     allocate channel dev1 type disk;  
     set until logseq 1234 thread 1;
     restore database skip tablespace readonly;  
     recover database;  
     sql "ALTER DATABASE OPEN RESETLOGS";
     release channel dev1;
}
reset database;

Resetting an Old Incarnation

The following command makes an old incarnation of database PROD1 current again:

# obtain primary key of old incarnation
list incarnation of database prod1;

List of Database Incarnations
DB Key  Inc Key   DB Name   DB ID       CUR    Reset SCN    Reset Time
------- -------   -------   ------      ---    ----------   ----------
1       2         PROD1     1224038686  NO     1            02-JUL-98
1       582       PROD1     1224038686  YES    59727        10-JUL-98

shutdown immediate;
# reset database to old incarnation
reset database to incarnation 2;
# recover it
run {  
     allocate channel dev1 type disk;
     restore controlfile;
     startup mount;
     restore database;
     recover database;
     sql "ALTER DATABASE OPEN RESETLOGS";
     release channel dev1;
}

Related Topics

"list"

"restore"

"recover"



Malik, Fawzia wrote:
          Hi,
 
Please can someone explain the consequences of "reset database" in rman?? Does this mean all the previous backups are lost??Is there a way around ??
 
Any help/advice would be greatly appreciated...
 
 
Rgds
 
Fawzia


**********************************************************************
Information in this email is confidential and may be privileged.
It is intended for the addressee only. If you have received it in error,
please notify the sender immediately and delete it from your system.
You should not otherwise copy it, retransmit it or use or disclose its
contents to anyone.
Thank you for your co-operation.
**********************************************************************

-- 

/regards

Peter Gram

Mobil : +45 2527 7107
Fax   : +45 4466 8856

Miracle A/S
Kratvej 2
2760 Måløv
http://miracleas.dk

/*
The process of preparing programs for a digital computer is especially
attractive, not only because it can be economically and scientifically
rewarding, but also because it can be an aesthetic experience much like 
composing poetry or music

Donald Knuth
*/ 



The previous attachment was filtered out by the ListGuru mailing software at fatcity.com because binary attachments are not appropriate for mailing lists. If you want a copy of the attachment which was removed, contact the sender directly and ask for it to be sent to you by private E-mail.

This warning is inserted into all messages containing binary attachments which have been removed by ListGuru. If you have questions about this message, contact Postmaster_at_fatcity.com for clarification.









Oracle Documentation Library, Release 8.1.7


Please select a product from the list of documentation available on this system:

Contacting Oracle Support Services and Ordering Printed Books

Please visit the following web addresses for Oracle product support and ordering information:


We Want to Hear From You

We are always trying to improve the content and delivery of our online documentation, so we invite you to tell us what you think. Each document in this distribution includes a reader's comment form, with an appropriate e-mail address for submitting comments on that document.

If you have general comments about the documentation library or this CD-ROM, please send them to doc_talk@us.oracle.com. Please note that this address is only for documentation feedback. For assistance with installation or software problems, please contact Oracle Support Services using the URLs listed above.


Oracle Corporation
Copyright © 1996-2000 Oracle Corporation
500 Oracle Parkway, Redwood City, CA 94065


The previous attachment was filtered out by the ListGuru mailing software at fatcity.com because binary attachments are not appropriate for mailing lists. If you want a copy of the attachment which was removed, contact the sender directly and ask for it to be sent to you by private E-mail.

This warning is inserted into all messages containing binary attachments which have been removed by ListGuru. If you have questions about this message, contact Postmaster_at_fatcity.com for clarification.





   Oracle8i Server and SQL*Plus
   
   



Oracle8i Server and SQL*Plus Go to Product Documentation Library
Library


Not all manuals in the library have been updated for this release. The header
at the top of each HTML page indicates the most recent revision for that document.
An asterisk (*) by a title indicates that a manual is from Release 8.1.6 and that
some updated information can be found in the Oracle8i Documentation Addendum.

This library also includes Windows-specific Server and SQL*Plus documentation.



Administration, Concepts, and Reference

Getting to Know Oracle8i
HTML PDF
Oracle8i Administrator's Guide
HTML PDF
Oracle8i Concepts
HTML PDF
Oracle8i Designing and Tuning for Performance *
HTML PDF
Oracle8i Error Messages *
HTML PDF
Oracle8i Migration
HTML PDF
Oracle8i National Language Support Guide *
HTML PDF
Oracle8i Reference *
HTML PDF
Oracle8i SQL Reference
HTML PDF
Oracle8i Supplied Java Packages Reference
HTML PDF
Oracle8i Supplied PL/SQL Packages Reference *
HTML PDF
Oracle8i Utilities
HTML PDF

Backup and Recovery

Oracle8i Backup and Recovery Guide
HTML PDF
Oracle8i Recovery Manager User's Guide and Reference *
HTML PDF
Oracle8i Standby Database Concepts and Administration *
HTML PDF
Legato Storage Manager Administrator's Guide
HTML PDF

SQL*Plus

SQL*Plus User's Guide and Reference
HTML PDF
SQL*Plus Quick Reference
HTML PDF
SQL*Plus Accessibility Guide for Windows
HTML PDF

Data Warehousing

Oracle8i Data Warehousing Guide
HTML PDF

Distributed Databases and Replication

Oracle8i Distributed Database Systems
HTML PDF
Oracle8i Replication *
HTML PDF
Oracle8i Replication Management API Reference *
HTML PDF


The previous attachment was filtered out by the ListGuru mailing software at fatcity.com because binary attachments are not appropriate for mailing lists. If you want a copy of the attachment which was removed, contact the sender directly and ask for it to be sent to you by private E-mail.

This warning is inserted into all messages containing binary attachments which have been removed by ListGuru. If you have questions about this message, contact Postmaster_at_fatcity.com for clarification.











Oracle8i Recovery Manager User's Guide and Reference -- Contents
	   










       




Oracle8i Recovery Manager User's Guide and Reference
Release 2 (8.1.6)

Part Number A76990-01

Library

Product

Index

Updated information for Release 8.1.7 can be found in the Oracle8i Documentation Addendum.
Go to next page

Contents

Title and Copyright Information

Send Us Your Comments

Preface

What's New in Oracle8i?
Release 8.1.6
Release 8.1.5
Structure
Changes to This Book
Audience
Knowledge Assumed of the Reader
Conventions
Text
Recovery Manager Syntax Diagrams and Notation
Code Examples
How to Use This Guide
Your Comments Are Welcome

Part I Using Recovery Manager

1 Recovery Manager Concepts

Overview of Recovery Manager
Recovery Manager Features
What Recovery Manager Is Not
Recovery Manager Commands
Recovery Manager PL/SQL Packages
How Recovery Manager Compiles and Executes Commands
Types of Recovery Manager Commands
User Execution of Recovery Manager Commands
User Termination of Recovery Manager Commands
Recovery Manager Command Errors
Recovery Manager Repository
Storage of the RMAN Repository in the Recovery Catalog
Storage of the RMAN Repository Exclusively in the Control File
Media Management
Backup and Restore Operations Using a Media Manager
Media Manager Crosschecks
Proxy Copy
Media Manager Testing
Backup Solutions Program
Lists and Reports
Lists of Backups and Copies
Reports on Backups, Copies, and Database Schema
Channel Allocation
Channel Control Options
Channel Parallelization
Backup Sets
Storage of Backup Sets
Backup Set Compression
Filenames for Backup Pieces
Number and Size of Backup Sets
Size of Backup Pieces
Multiplexed Backup Sets
Duplexed Backup Sets
Parallelization of Backups
Backup Errors
Backup Types
Full Backups
Incremental Backups
Backup Constraints
Image Copies
RMAN Image Copies
O/S Image Copies
Tags for Backups and Image Copies
Restoring Files
Mechanics of Restore Operations
File Selection in Restore Operations
Restore Constraints
Media Recovery
Application of Incremental Backups and Redo Records
Incomplete Recovery
Tablespace Point-in-Time Recovery
Database Duplication
Integrity Checks
Detection of Physical Block Corruption
Detection of Logical Block Corruption
Detection of Fractured Blocks During Open Backups

2 Getting Started with Recovery Manager

Setting Up Recovery Manager
Using Password Files
Setting NLS Environment Variables
Determining the Snapshot Control File Location
Using RMAN with a Multi-Threaded Server
Deciding Whether to Use a Recovery Catalog
Consequences of Using the Recovery Catalog as the RMAN Repository
Consequences of Using the Control File as the RMAN Repository
Connecting to RMAN
Connecting to RMAN Without a Recovery Catalog
Connecting to RMAN with a Recovery Catalog
Connecting to an Auxiliary Database
Hiding Passwords When Connecting to RMAN
Disconnecting from RMAN
Using Basic RMAN Commands
Connecting to RMAN
Mounting the Database
Reporting the Current Schema
Copying a Datafile
Backing Up a Tablespace
Listing Backups and Copies
Validating a Restore
Configuring a Media Manager
Linking with a Media Manager
Generating Unique Filenames
Limiting File Size
Sending Device-Specific Strings to the Media Manager
Troubleshooting the Media Manager
Using Sample Scripts and Scenarios

3 Managing the Recovery Manager Repository

Creating the Recovery Catalog
Setting Recovery Catalog Compatibility
Maintaining the RMAN Repository
Registering a Database with the Recovery Catalog
Unregistering a Database from the Recovery Catalog
Resetting the Recovery Catalog
Changing the Availability of a Backup or File Copy
Crosschecking the RMAN Repository
Deleting Backups and Copies and Updating Their Status in the RMAN Repository
Validating the Restore of Backups and Copies
Storing Scripts in the Recovery Catalog
Resynchronizing the Recovery Catalog
Managing Records in the Control File
Cataloging Operating System Backups
Backing Up and Recovering the Recovery Catalog
Backing Up the Recovery Catalog
Recovering the Recovery Catalog
Re-Creating the Recovery Catalog
Upgrading the Recovery Catalog
Dropping the Recovery Catalog
Managing the RMAN Repository Without a Recovery Catalog
Understanding Catalog-Only Command Restrictions
Monitoring the Overwriting of Control File Records
Maintaining the Control File Repository
Backing Up the Control File

4 Generating Lists and Reports with Recovery Manager

Using Lists and Reports in Your Backup and Recovery Strategy
Generating Lists
Generating Reports
List and Report Scenarios
Makings Lists of Backups and Copies
Using Lists to Determine Obsolete Backups and Copies
Reporting Datafiles Needing Backups
Reporting Unrecoverable Datafiles
Reporting Obsolete Backups and Copies
Manually Deleting Obsolete Backups and Copies
Deleting Obsolete Backups and Copies Using a UNIX Shell Script
Generating Historical Reports of Database Schema
Listing Database Incarnations
Reporting Deleted Backups and Copies

5 Making Backups and Copies with Recovery Manager

Making Backups
Making Consistent and Inconsistent Backups
Making Whole Database Backups
Backing Up Tablespaces and Datafiles
Backing Up Control Files
Backing Up Archived Redo Logs
Making Incremental Backups
Making Split Mirror Backups
Making Image Copies
Backup and Copy Scenarios
Reporting Datafiles Needing Backups
Skipping Files when Backing Up a Database
Spreading a Backup Across Multiple Disk Drives
Backing Up a Large Database to Multiple Filesystems
Specifying the Size of Backup Sets
Specifying the Size of Backup Pieces
Multiplexing Datafiles in a Backup
Backing Up Archived Redo Logs
Backing Up and Deleting Multiple Copies of an Archived Redo Log
Performing Differential Incremental Backups
Performing Cumulative Incremental Backups
Duplexing Backup Sets
Determining How Channels Distribute a Backup Workload
Backing Up in NOARCHIVELOG Mode
Backing Up in a Parallel Server Environment
Cataloging Operating System Copies
Maintaining Backups and Copies
Handling Errors During Backups and Copies

6 Restoring and Recovering with Recovery Manager

Restoring Datafiles, Control Files, and Archived Redo Logs
Restoring a Database
Restoring Tablespaces and Datafiles
Restoring Control Files
Restoring Archived Redo Logs
Restoring in Preparation for Incomplete Recovery
Restoring in an OPS Configuration
Recovering Datafiles
Preparing for Media Recovery
Performing Complete Recovery
Performing Incomplete Recovery
Restore and Recovery Scenarios
Restoring Datafile Copies to a New Host
Restoring When Multiple Databases Share the Same Name
Restoring the Control File from a Backup Set Without Using RMAN
Recovering an Inaccessible Datafile in an Open Database
Recovering an Inaccessible Datafile Using Backups from Disk and Tape
Performing Recovery After a Total Media Failure
Recovering a Pre-RESETLOGS Backup
Recovering a Database in NOARCHIVELOG Mode
Recovering a Lost Datafile Without a Backup

7 Creating a Duplicate Database with Recovery Manager

Creating a Duplicate Database: Overview
Obeying Restrictions
Generating Files for the Duplicate Database
Preparing the Auxiliary Instance for Duplication
Creating a Duplicate Database on a Local or Remote Host
Duplicating a Database on a Remote Host with the Same Directory Structure
Duplicating a Database on a Remote Host with a Different Directory Structure
Creating a Duplicate Database on the Local Host
Duplication Scenarios
Setting New Filenames Manually
Resynchronizing the Duplicate Database with the Target Database
Creating a Non-Current Duplicate Database

8 Performing Point-in-Time Recovery with Recovery Manager

Introduction to RMAN TSPITR
Planning for TSPITR
Performing TSPITR Without a Recovery Catalog
Understanding General Restrictions
Researching and Resolving Inconsistencies
Managing Data Relationships
Preparing the Auxiliary Instance for TSPITR
Performing TSPITR
Preparing the Target Database for Use After TSPITR
Responding to Unsuccessful TSPITR
Tuning TSPITR Performance
Specify a New Name for Datafiles in Auxiliary Set Tablespaces
Set the Auxiliary Name and Use a Datafile Copy for Recovery Manager TSPITR
Use the Converted Filename in the Auxiliary Control File
Summary: Datafile Naming Methods

9 Recovery Manager Troubleshooting

Interpreting Message Output
Identifying Types of Message Output
Identifying Error Codes
Interpreting RMAN Error Stacks
Interpreting Debugging Output
Testing the Media Management API
Obtaining the Utility
Obtaining Online Documentation
Using the Utility
Monitoring RMAN Jobs
Correlating Server Sessions with Channels
Monitoring Job Progress
Monitoring Job Performance
Terminating an RMAN Session
Components of an RMAN Session
Process Behavior During a Hung Job
Terminating an RMAN Session
Troubleshooting Scenarios
After Linking to the Media Manager on UNIX, RMAN Fails to Back Up to Tape
After Installing the Media Manager on NT, RMAN Fails to Back Up to Tape
Backup Job Is Hanging
RMAN Fails to Start RPC Call
Backup Fails with Invalid RECID Error
Backup Fails Because of Control File Enqueue
RMAN Fails to Delete All Archived Logs
Backup Fails Because RMAN Cannot Locate an Archived Log
RMAN Issues Character Set Errors When You Attempt to Connect to the Target
RMAN Denies Logon to Target Database
Database Duplication Fails with RMAN-20240
UNKNOWN Database Name Appears in Recovery Catalog

Part II Recovery Manager Reference

10 Recovery Manager Command Syntax

Conventions Used in this Reference
Command Entries
Summary of RMAN Commands
allocate
allocateForMaint
alterDatabase
archivelogRecordSpecifier
backup
catalog
change
cmdLine
completedTimeSpec
configure
connect
connectStringSpec
copy
createCatalog
createScript
crosscheck
datafileSpec
debug
deleteExpired
deleteScript
deviceSpecifier
dropCatalog
duplicate
host
list
listObjList
printScript
recover
register
release
releaseForMaint
replaceScript
replicate
report
reset
restore
resync
rmanCommand
run
send
set
set_run_option
shutdown
sql
startup
switch
untilClause
upgradeCatalog
validate

11 Recovery Catalog Views

RC_ARCHIVED_LOG
RC_BACKUP_CONTROLFILE
RC_BACKUP_CORRUPTION
RC_BACKUP_DATAFILE
RC_BACKUP_PIECE
RC_BACKUP_REDOLOG
RC_BACKUP_SET
RC_CHECKPOINT
RC_CONTROLFILE_COPY
RC_COPY_CORRUPTION
RC_DATABASE
RC_DATABASE_INCARNATION
RC_DATAFILE
RC_DATAFILE_COPY
RC_LOG_HISTORY
RC_OFFLINE_RANGE
RC_PROXY_CONTROLFILE
RC_PROXY_DATAFILE
RC_REDO_LOG
RC_REDO_THREAD
RC_RESYNC
RC_STORED_SCRIPT
RC_STORED_SCRIPT_LINE
RC_TABLESPACE

Glossary

Index


The previous attachment was filtered out by the ListGuru mailing software at fatcity.com because binary attachments are not appropriate for mailing lists. If you want a copy of the attachment which was removed, contact the sender directly and ask for it to be sent to you by private E-mail.

This warning is inserted into all messages containing binary attachments which have been removed by ListGuru. If you have questions about this message, contact Postmaster_at_fatcity.com for clarification.











Oracle8i Recovery Manager User's Guide and Reference -- Index
	   










       




Oracle8i Recovery Manager User's Guide and Reference
Release 2 (8.1.6)

Part Number A76990-01

Library

Product

Contents

Go to previous page

Index

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W 


A

alert log
control file record messages, 3-47
monitoring overwriting of control file records, 3-48
useful for RMAN, 9-2
allocate channel command (RMAN), 10-10
and multi-threaded server, 10-11, 10-15
for delete option, 5-27, 10-14
for maintenance option, 10-14
alter database command (RMAN), 10-16
ALTER DATABASE statement
OPEN RESETLOGS clause, 3-12
RENAME DATABASE clause, 6-10
ALTER TABLESPACE statement
BEGIN/END BACKUP clause, 3-35
archived redo logs
backing up, 5-20
using RMAN, 5-9, 5-10
cataloging, 3-9
copies, listing, 4-2
restoring using RMAN, 6-14
RMAN fails to delete, 9-30
archivelogRecoverSpecifier clause (RMAN), 10-18
auxiliary databases
for RMAN TSPITR
converted filenames, 8-15
using datafile copies, 8-14
auxiliary sets
for RMAN TSPITR, 8-4
naming datafiles in tablespaces, 8-13
available option (RMAN)
change command, 3-13

B

backup command (RMAN), 1-33, 5-2, 5-28, 10-22
proxy only option, 1-22
proxy option, 1-22
skip offline option, 5-16
backup pieces
restricting size, 1-41, 10-145
backup sets
creating using backup command, 1-39
crosschecking, 3-15
duplexing, 5-23
errors during creation, 1-47
listing, 4-2
multiplexing, 1-42
naming, 1-35
organizing, 1-33
parallelizing creating of, 1-45
restoring without RMAN, 6-37
restricting piece size, 1-41
specifying maximum size (in bytes), 1-39, 1-41
specifying number of, 1-35
testing restore of, 3-24
Backup Solutions Program (BSP), 1-23
Legato Storage Manager (LSM), 1-23
BACKUP_TAPE_IO_SLAVES initialization parameter, 5-24
backups
archived redo logs, 5-20
backing up using RMAN, 5-10
using RMAN, 5-9
automatic location using RMAN, 6-17
backup command (RMAN), 5-2
backup sets, 1-32
control file
using for recovery, 6-22
using RMAN, 5-7
correlating RMAN channels with, 9-14
cumulative incremental, 1-53, 1-54, 1-62, 1-65, 5-23
datafile
using RMAN, 5-5, 5-6
duplexing, 5-23
failed RMAN, 9-31
full, 1-49
generating reports for, 4-2
hung, 9-23
image copies, 1-32, 1-57
incremental, 1-50, 5-22
differential, 1-51
using RMAN, 5-11
keeping, 5-27
NOARCHIVELOG mode, in, 5-25
noncumulative incremental, 1-52
Parallel Server Environment, 5-26
parallelization, 1-45, 5-24
recovering pre-RESETLOGS, 6-42
recovery catalog, 1-16
using control file as repository, 3-39
reporting objects needing backups, 4-5
RMAN error handling, 5-28
specifying number of files per set, 1-36
split mirror
using RMAN, 5-12
stored scripts, 3-27
tablespace
using RMAN, 5-5, 5-6
tags, 1-58
troubleshooting failed RMAN, 9-19, 9-22, 9-26, 9-29
types, 1-32
user-created, cataloging, 3-35
using RMAN, 5-2
whole database
using RMAN, 5-3
BEGIN/END clause
ALTER TABLESPACE statement, 3-35
BSP. See Backup Solutions Program

C

cancelling RMAN commands, 1-12
CASE1.RCV sample script
setting size limits for backup pieces, 2-21
catalog command (RMAN), 3-9, 3-34, 10-35
cataloging
archived redo logs, 3-9
datafiles, 3-9
cataloging operating system copies, 5-27
CATALOG.SQL script, 3-2
CATPROC.SQL script, 3-2
CATRMAN.SQL script, 3-10
change command (RMAN), 3-15, 10-38
available option, 3-13
delete option, 3-20, 3-36
unavailable option, 3-13
channels
allocating, 1-28
allocating to MTS sessions, 10-11, 10-15
controlling RMAN, 1-28
managing RMAN, 1-28
parellelization of, 1-31
character sets
RMAN errors, 9-32
setting for use with RMAN, 2-3
code examples
description of, 10-5
command files
Recovery Manager, 1-10
command line
arguments for RMAN, 1-10, 10-42
commands, Recovery Manager
allocate channel, 10-10
allocate channel for delete, 5-27
allocate channel for maintenance/delete, 10-14
alter database, 10-16
archivelogRecoverSpecifier clause (RMAN), 10-18
backup, 1-33, 5-2, 5-28, 10-22
proxy only option, 1-22
proxy option, 1-22
skip offline option, 5-16
catalog, 3-9, 3-34, 10-35
change, 3-15, 10-38
delete option, 3-36
configure, 10-47
connect, 10-51, 10-53
copy, 10-55
create catalog, 10-59
create script, 10-61
crosscheck, 10-64
debug, 10-68
delete expired backup, 10-69
delete script, 10-71, 10-72
drop catalog, 3-44, 10-74
duplicate, 1-64, 10-76
execute script, 3-27
host, 10-81
list, 1-24, 10-83
incarnation of database option, 3-13
listObjList clause, 10-92
overview, 1-5
print script, 10-94
recover, 1-61, 6-18, 10-96
register, 3-10, 10-101
release channel, 10-103
release channel (of type maintenance), 10-104
replace script, 10-105
replicate, 6-12, 10-108
replicate controlfile, 6-12
report, 1-26, 10-110
need backup option, 4-5
reset database, 3-12, 10-118
incarnation option, 3-13
restore, 6-19, 10-120
resync catalog, 1-15, 3-29, 10-127
from controlfilecopy option, 3-43
rman, 10-130
run, 10-133
send, 2-22, 10-136
set, 10-138
duplex parameter, 5-24
maxcorrupt for datafile option, 5-28
newname for datafile option, 6-10
set (within run command), 10-142
shutdown, 10-147
sql, 10-150
startup, 10-152
summary, 10-6
switch, 10-154
terminating, 1-12
until, 10-45, 10-156
upgrade catalog, 3-43, 10-158
validate, 10-160
compatibility
level of recovery catalog, 1-16
recovery catalog
viewing parameter setting, 3-6
Recovery Manager. See Oracle8i Migration
compilation and execution of RMAN commands, 1-6
complete recovery
using RMAN, 6-20
configuration of RMAN
for use with MTS, 2-4
configure compatible command (RMAN), 1-16, 3-4
connect command (RMAN), 10-51, 10-53
connection options
Recovery Manager, 2-9
auxiliary database, 2-12
hiding passwords, 2-13
with a catalog, 2-10
without a catalog, 2-9
constraints
restore, 1-60
control file records
overwriting, 3-47
control files
backing up
using RMAN, 5-7
backup and recovery, 6-22
overwriting records, 3-47
restoring, 6-12
using dbid, 6-36
using RMAN, 6-12, 6-13
snapshot
specifying location of, 2-3
using instead of a recovery catalog, 1-17
CONTROL_FILE_RECORD_KEEP_TIME initialization parameter, 3-47
preventing overwrite of RMAN records, 3-47
CONTROL_FILES initialization parameter, 6-12, 8-8
copy command (RMAN), 10-55
corrupt datafile blocks
detecting, 1-66, 1-67
maximum acceptable number, 10-143
records in control file, 1-48
RMAN and, 1-47
setting maximum for backup, 5-28
corruption detection, 1-66, 1-67
using set maxcorrupt command, 10-143
create catalog command (RMAN), 10-59
CREATE CONTROLFILE statement
and recovery, 6-18
create script command (RMAN), 10-61
creating
duplicate databases, 7-2
on a remote host, 7-10
recovery catalog, 3-2
test databases, 1-64
crosscheck command (RMAN), 10-64
crosschecking
definition, 1-21
recovery catalog with the media manager, 3-14
cumulative incremental backups, 1-53, 5-23

D

database schema
generating reports, 4-8
databases
backing up
using Recovery Manager, 1-33
creating duplicate, 7-2
on a remote host, 7-10
creating test, 7-2
db identifier, 3-10
registering in recovery catalog, 3-9
unregistering in recovery catalog, 3-11
datafiles
backing up
using Recovery Manager, 1-33, 5-5, 5-6
backups needed, listing, 4-10, 4-11, 4-13, 5-16
backups, listing, 4-2
cataloging, 3-9
copies, listing, 4-2
listing
unrecoverable, 4-5
recovery
guidelines, 1-61, 6-18
using RMAN, 6-18
restoring, 1-59, 6-2, 6-10
dates
specifying in RMAN commands, 2-3
db identifier, 3-10
obtaining, 6-35
problems registering copied database, 3-10
DB_FILE_NAME_CONVERT initialization parameter, 1-65, 8-8
using with RMAN duplicate command, 7-7
DB_NAME initialization parameter, 8-8
debug command (RMAN), 9-8, 10-68
debugging RMAN, 9-8
delete expired backup command (RMAN), 3-21, 10-69
delete script command (RMAN), 10-71, 10-72
deleting
backups and image copies, 3-20
obsolete backups and copies, 3-21
differential incremental backups, 1-51
disconnecting
from Recovery Manager, 2-13
disk API, 9-19
disk buffers
tuning for RMAN backups. See Oracle8i Tuning, 1-35
diskratio parameter
backup command (RMAN), 10-29
drop catalog command (RMAN), 10-74
dropping the recovery catalog, 3-44
dummy API, 9-19
duplex parameter (RMAN)
set command, 5-24
duplexing backup sets, 1-44, 5-23
duplicate command (RMAN), 1-64, 10-76
duplicate databases
creating, 1-64, 7-2
non-current, 7-19
on a remote host with same filesystem, 7-11
on local host, 7-17
on remote host with different filesystem, 7-12
DB_FILE_NAME_CONVERT initialization parameter, 7-5
failed creation, 9-33
generating filenames, 7-3
nofilenamecheck option, 7-6
restrictions, 7-3
set auxname command (RMAN), 7-5
set newname command (RMAN), 7-5
skipping offline normal tablespaces, 7-6
skipping read-only tablespaces, 7-5
duplicating a database, 1-64
troubleshooting, 9-33

E

environment variables
NLS_DATE_FORMAT, 2-2
NLS_LANG, 2-2
error codes
media manager, 9-4
RMAN, 9-2, 9-3
error stacks
interpreting, 9-6
errors
during RMAN backups, 5-28
Recovery Manager, 1-13
expired records
removing from recovery catalog, 3-21

F

features, new
autolocate option, xv
configure compatible command, xvi
create catalog command, xvii
crosscheck commands, xvi
drop catalog command, xvii
duplexed backup sets, xvii
duplicate command, xvii
media management API 2.0, xvi
remove records from recovery catalog, xvi
report need backup redundancy command, xvii
resetlogs option in RMAN, xvi
RMAN disk affinity, xvii
RMAN TSPITR without catalog, xviii
startup, shutdown, and alter database in RMAN, xvii
unique names for backup pieces by default, xvii
upgrade catalog command, xvii
V$BACKUP_SYNC_IO and V$BACKUP_ASYNC_IO, xviii
filesperset parameter
backup command (RMAN), 10-27
specifying number of files in a backup set, 1-36
fractured block detection, 1-67
full backups, 1-49

G

generating lists using RMAN, 1-24
generating reports, 1-24, 4-5

H

host command (RMAN), 10-81

I

image copies, 1-57
crosschecking, 3-17
testing restore of, 3-24
incarnation of database option (RMAN)
list command, 3-13
incarnation option (RMAN)
reset database command, 3-13
incomplete recovery
change-based (RMAN), 6-27
log sequence-based (RMAN), 6-28
restoring in preparation for, 6-16
time-based (RMAN), 6-26
using RMAN, 6-25
with a recovery catalog, 6-26
without a recovery catalog, 6-29, 6-31
incremental backups, 5-22
differential, 1-51
using RMAN, 5-11
initialization parameter file, 1-61, 6-18
initialization parameters
BACKUP_TAPE_IO_SLAVES, 5-24
CONTROL_FILES, 6-12
integrity checking, 1-66
interpreting RMAN error stacks, 9-6
I/O errors
effect on backups, 1-47

J

jobs
RMAN, 1-9
monitoring performance, 9-17
monitoring progress, 9-14

K

kbytes parameter
set command (RMAN), 1-41, 2-21
keywords
in syntax diagrams, 10-3

L

level 0 incremental backups, 1-50
list command (RMAN), 1-24, 10-83
incarnation of database option, 3-13
listObjList clause (RMAN), 10-92
lists (RMAN), 4-2 to 4-4
backups and copies, 4-3, 4-10
backups and copies made before specified date, 4-10
scenarios, 4-10
LOCK_NAME_SPACE initialization parameter, 8-8
log switches
recovery catalog records, 3-34
LOG_FILE_NAME_CONVERT initialization parameter, 8-8

M

managing RMAN metadata, 3-1, 7-1
maxcorrupt parameter
set command (RMAN), 10-143
media management
backing up files, 1-20
Backup Solutions Program, 1-23
Legato Storage Manager (LSM), 1-23
crosschecking, 1-21
error codes, 9-4
linking to software, 2-20
maximum file size, 2-21
proxy copy, 1-22
relinking to the API, 9-21
requirements, 2-20
restoring files, 1-21
sbttest program, 1-23, 9-10
sending device-specific strings, 2-22
testing the API, 9-10
troubleshooting, 2-22
unique filenames, generating, 2-21
Media Management Library (MML), 1-20
media recovery
datafiles
guidelines for, 1-61, 6-18
using Recovery Manager, 1-61, 6-18
metadata
managing RMAN, 1-13, 3-1, 7-1
storing in control file, 1-17
mirrored files
splitting
using RMAN, 5-12
mirroring
backups using, 5-12
monitoring RMAN, 9-12
multiplexing
datafiles with Recovery Manager, 1-42
multi-threaded server
allocating channels, 10-11, 10-15
configuring for use with RMAN, 2-4

N

name translation
for RMAN commands, 1-7
naming backup sets, 1-35
new features
autolocate option, xv
configure compatible command, xvi
create catalog command, xvii
crosscheck commands, xvi
drop catalog command, xvii
duplexed backup sets, xvii
duplicate command, xvii
media management API 2.0, xvi
remove records from recovery catalog, xvi
report need backup redundancy command, xvii
resetlogs option in RMAN, xvi
RMAN disk affinity, xvii
RMAN TSPITR without catalog, xviii
startup, shutdown, and alter database in RMAN, xvii
unique names for backup pieces by default, xvii
upgrade catalog command, xvii
V$BACKUP_SYNC_IO and V$BACKUP_ASYNC_IO, xviii
newname for datafile option (RMAN)
set command, 6-10
NLS_DATE_FORMAT environment variable, 2-2, 5-21, 6-26
NLS_LANG environment variable, 2-2, 5-21, 6-26
NOARCHIVELOG mode
backing up, 5-25
noncumulative incremental backups, 1-52
normalization
of pre-8.1.6 control file on NT, 10-123

O

objects owned by SYS
and TSPITR using RMAN, 8-6
open database backups
fractured block detection during, 1-67
open database recovery
using RMAN, 6-24
OPEN RESETLOGS clause
ALTER DATABASE statement, 3-12
operating system utilities
copying files with, 5-27
OPS. See Oracle Parallel Server
Oracle Parallel Server
backups and, 5-26
restoring using RMAN, 6-16
overwriting control file records, 3-47

P

Parallel Server. See Oracle Parallel Server
parallelization
channels, 1-31
factors affecting degree of, 1-31
of backups using RMAN, 1-45, 5-24
RMAN backups, 1-45, 5-24
parameters
in syntax diagrams, 10-3
password files
connecting to Recovery Manager with, 2-10, 2-11
connecting to Recovery Manager without, 2-11
Recovery Manager, 2-2
passwords
hiding in RMAN, 2-13
point-in-time recovery
tablespace, 8-2 to 8-15
PRGRMANC.SQL script, 3-19
print script command (RMAN), 10-94
proxy copy
overview, 1-22
proxy only option (RMAN)
backup command, 1-22
proxy option (RMAN)
backup command, 1-22
purging recovery catalog
obsolete records, 3-19
records with DELETED status, 3-19

Q

querying
recovery catalog, 4-2

R

RC_ARCHIVED_LOG view, 11-2
RC_BACKUP_CONTROLFILE view, 11-3
RC_BACKUP_CORRUPTION view, 11-5
RC_BACKUP_DATAFILE view, 11-6
RC_BACKUP_PIECE view, 11-8
RC_BACKUP_REDOLOG view, 11-9
RC_BACKUP_SET view, 11-11
RC_CHECKPOINT_VIEW, 11-12
RC_CONTROLFILE_COPY view, 11-13
RC_COPY_CORRUPTION view, 11-14
RC_DATABASE view, 11-15
RC_DATABASE_INCARNATION view, 11-15
RC_DATAFILE view, 11-16
RC_DATAFILE_COPY view, 11-17
RC_LOG_HISTORY view, 11-18
RC_OFFLINE_RANGE view, 11-19
RC_PROXY_CONTROLFILE view, 11-20
RC_PROXY_DATAFILE view, 11-22
RC_REDO_LOG view, 11-24
RC_REDO_THREAD view, 11-24
RC_RESYNC view, 11-25
RC_STORED_SCRIPT view, 11-25
RC_STORED_SCRIPT_LINE view, 11-26
RC_TABLESPACE view, 11-26
read-only tablespaces
backing up, 5-16
recover command (RMAN), 1-61, 6-18, 10-96
recovery
complete using RMAN, 6-20
database
in NOARCHIVELOG mode, 6-43
disaster using RMAN, 6-39
inaccessible datafiles
in open database, 6-38
using disk and tape backups, 6-39
incomplete, 6-25
without a recovery catalog, 6-31
without recovery catalog, 6-29
of lost or damaged recovery catalog, 3-42
open database using RMAN, 6-24
preparing for, 6-19
skipping tablespaces during, 6-20
tablespace, 6-23
to log sequence number, 6-28
to SCN, 6-27
to time, 6-26
using backup control file (RMAN), 6-22
using RMAN, 6-18
whole database
using backup control file, 6-22
when control file is intact, 6-21
recovery catalog, 1-14, 2-6 to 3-43
and incomplete recovery, 6-26
backing up, 1-16
using control file as repository, 3-39
cataloging
O/S backups, 3-34
changing availability of backup, 3-13
changing status of backups to DELETED, 3-18
compatibility, 1-16
viewing, 3-6
compatibility. See Oracle8i Migration
connecting to Recovery Manager with, 2-10, 2-12
connecting to Recovery Manager without, 2-9, 2-11
consequences of using, 2-6
creating, 3-2
8.1.6 catalog usable with pre-8.1.6 RMAN, 3-6
in separate database, 2-6
crosschecking, 3-14
db identifier problems, 3-10
deleting records, 3-20
dropping, 3-44
log switch record, 3-34
managing size of, 3-33
operating with, 1-14
operating without, 1-17
overview, 1-14
purging all records with DELETED status, 3-19
querying, 1-24, 4-2
recovery of lost or damaged, 3-42
refreshing, 3-29
registering databases, 3-9
registering target databases, 3-9
in two catalogs, 3-39
removing records, 3-23
expired, 3-21
obsolete, 3-19, 3-21
resynchronizing, 1-15, 3-29
schema, 2-6
setting up, 3-2
setting compatibility level, 3-4
snapshot control file, 1-15
stored scripts
creating, 3-27
executing, 3-28
UNKNOWN database name, 9-35
unregistering databases, 3-11
updating
after operating system deletions, 3-20
after schema changes, 3-32
upgrading, 3-43
views, 11-1
Recovery Manager
advantages to using, 1-4
allocate channel for maintenance, 10-14
backup sets, 1-39
backup types, 1-32
duplexed backup sets, 1-44
backups, 5-2
archived redo logs, 5-9,