Oracle Database B

Transcription

1 Oracle Database Backup and Recovery Advanced User s Guide 10g Release 2 (10.2) B November 2005 A guide to advanced backup and recovery of Oracle databases and advanced uses of Recovery Manager (RMAN), including advanced RMAN database backup and recovery concepts and scenarios, using RMAN for data migration, transport and duplication, and user-managed backup and recovery without RMAN.

2 Oracle Database Backup and Recovery Advanced User s Guide, 10g Release 2 (10.2) B Copyright 2003, 2005, Oracle. All rights reserved. Primary Author: Contributing Author: Antonio Romero Lance Ashdown Contributors: Tammy Bednar, Anand Beldalker, Timothy Chien, Raymond Guzman, Alex Hwang, Ashok Joshi, J. William Lee, Valarie Moore, Muthu Olagappan, Samitha Samaranayake, Francisco Sanchez, Steven Wertheimer, Wanli Yang The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR , Commercial Computer Software Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

3 Contents Preface... xxi Audience... Documentation Accessibility... Related Documentation... Conventions... xxi xxi xxii xxii What's New in Backup and Recovery?... xxiii Oracle Database 10g Release 2 New Features in Backup and Recovery... xxiii Part I Recovery Manager Advanced Architecture and Concepts 1 Recovery Manager Architecture About the RMAN Environment RMAN Session Architecture RMAN Command Line Client How RMAN Compiles and Executes Commands Compilation Phase Execution Phase Issuing RMAN Commands Entering Commands at the RMAN Prompt Using RMAN with Command Files Stored Scripts Commands Valid Only in RUN Blocks Commands Not Valid in RUN Blocks Directing RMAN Output to a Log File RMAN Repository Storage of the RMAN Repository in the Control File Types of Records in the Control File Recovery Without a Recovery catalog Storage of the RMAN Repository in the Recovery Catalog Registration of Databases in the Recovery Catalog Contents of the Recovery Catalog Resynchronization of the Recovery Catalog Backups of the Recovery Catalog Compatibility of the Recovery Catalog iii

4 Media Management Performing Backup and Restore with a Media Manager Backup Solutions Program RMAN Backups Concepts About RMAN Channels Automatic and Manual Channel Allocation Automatic Channel Device Configuration and Parallelism Automatic Channel Default Device Types Automatic Channel Naming Conventions Automatic Channel Generic Configurations Automatic Channel-Specific Configurations Clearing Automatic Channel Settings Determining Channel Parallelism to Match Hardware Devices Channel Control Options for Manual and Automatic Channels Channel Failover About RMAN Backups About Image Copies Using RMAN-Created Image Copies User-Managed Image Copies About Proxy Copies Storage of Backups on Disk and Tape Backups of Archived Logs Deletion of Archived Logs After Backups Backup Failover for Archived Redo Logs Multiplexed Backup Sets Algorithm for Multiplexed Backups Multiplexing by the Media Manager Manual Parallelization of Backups Multiple Copies of RMAN Backups Duplexed Backup Sets Backups of Backup Sets Uses for Backups of Backup Sets Backup Optimization When Backing Up Backup Sets Backup Failover When Backing Up Backup Sets Backups of Image Copies RMAN Backup Options: Naming, Sizing, and Speed Generating Filenames for RMAN Backup Pieces Generating Filenames for RMAN Image Copies Using FORMAT with RMAN BACKUP AS COPY Using DB_FILE_NAME_CONVERT With BACKUP AS COPY Using Tags to Identify RMAN Backups Default RMAN Backup Tag Format How Tags Are Applied Uniqueness of Backup Tags Size of Backup Pieces Number and Size of Backup Sets iv

5 Factors Affecting the Number and Size of Backup Sets Overview of the MAXSETSIZE Parameter I/O Read Rate of Backups RMAN Backup Types Incremental Backups Incremental Backup Algorithm Multilevel Incremental Backups Differential Incremental Backups Cumulative Incremental Backups Planning an Incremental Backup Strategy Control File and Server Parameter File Autobackups How RMAN Performs Control File Autobackups When RMAN Performs Control File Autobackups Control File Autobackups After Backup Acivities Control File Autobackups After Database Structural Changes Backup Retention Policies Recovery Window Backup Redundancy Batch Deletes of Obsolete Backups Exempting Backups from the Retention Policy Relationship Between Retention Policy and Flash Recovery Area Rules Backup Optimization Rules for Identifying Identical Files for Backup Optimization Backup Optimization Algorithm Requirements for Backup Optimization Overriding and Disabling Backup Optimization Effect of Retention Policies on Backup Optimization for SBT Backups Backup Optimization for SBT Backups with Recovery Window Retention Policy Backup Optimization for SBT Backups With Redundancy Retention Policy Restartable Backups Managing Backup Windows and Performance: BACKUP... DURATION Controlling RMAN Behavior when Backup Window Ends with PARTIAL Managing Backup Performance with MINIMIZE TIME and MINIMIZE LOAD How RMAN Responds to Backup Errors Handling I/O Errors in RMAN Backup: NOT BACKED UP SINCE Handling Corrupt Datafile Blocks in RMAN Backup: MAXCORRUPT Tests and Integrity Checks for Backups Detecting Physical Block Corruption With RMAN BACKUP... VALIDATE Detection of Logical Block Corruption Detection of Fractured Blocks During Open Backups Backup Validation with RMAN RMAN Recovery Concepts Restoring Files with RMAN Mechanics of Datafile Restore Operations How RMAN Selects Backups for Use in Restore Operations Restore Failover v

6 Restore Optimization Datafile Media Recovery with RMAN RMAN Media Recovery: Basic Steps Mechanics of Recovery: Incremental Backups and Redo Logs How RMAN Searches for Archived Redo Logs During Recovery RMAN Behavior When the Repository Is Not Synchronized Incomplete or Point-In-Time Recovery Tablespace Point-in-Time Recovery Block Media Recovery with RMAN When to Use Block Media Recovery Block Media Recovery When Redo Is Missing Database Duplication with RMAN Physical Standby Database Creation with RMAN Connecting to Databases with RMAN Starting RMAN Without Connecting to a Database Connecting to a Target Database and a Recovery Catalog Connecting to the Target Database and Recovery Catalog from the Command Line Connecting to the Target Database and Recovery Catalog from the RMAN Prompt Connecting to an Auxiliary Database Connecting to an Auxiliary Database from the Command Line Connecting to an Auxiliary Database from the RMAN Prompt Diagnosing Connection Problems Diagnosing Target and Auxiliary Database Connection Problems Diagnosing Recovery Catalog Connection Problems Hiding Passwords When Connecting to Databases Sending RMAN Output Simultaneously to the Terminal and a Log File Using the RMAN Pipe Interface Executing Multiple RMAN Commands In Succession Through a Pipe: Example Executing RMAN Commands In a Single Job Through a Pipe: Example Part II Advanced RMAN Backup and Recovery Topics 5 Configuring the RMAN Environment: Advanced Topics Configuring the Flash Recovery Area: Advanced Topics Configuring Online Redo Log Creation in the Flash Recovery Area Configuring Control File Creation in the Flash Recovery Area Archived Redo Log Creation in the Flash Recovery Area Rules for Initialization Parameters Affecting Redo Log File Destinations Filenames for Archived Redo Log Files in the Flash Recovery Area RMAN File Creation in the Flash Recovery Area Configuring RMAN to Make Backups to a Media Manager Prerequisites for Using a Media Manager with RMAN Locating the Media Management Library: The SBT_LIBRARY Parameter Testing Whether the Media Manager Library Is Integrated Correctly Configuring Media Management Software for RMAN Backups vi

7 Configuring Backup Piece Names and Sizes for a Media Manager Testing ALLOCATE CHANNEL on the Media Manager Testing a Backup to the Media Manager Configuring SBT Channels for Use with a Media Manager Configuring Channels Configuring Channel Parallelism Configuring Channel Settings for a Device Type Showing the Configured Channel Settings Showing the Currently Configured Channel Settings Showing the Configured Device Types Showing the Default Device Type Manually Overriding Configured Channels Configuring a Specific Channel for a Device Type Configuring Specific Channels: Examples Mixing Generic and Specific Channels Relationship Between CONFIGURE CHANNEL and Parallelism Setting Clearing Channel and Device Settings Configuring the Maximum Size of Backup Sets and Pieces Showing the Default Maximum Size of Backup Sets: SHOW MAXSETSIZE Configuring Backup Optimization Displaying Backup Optimization Setting: SHOW BACKUP OPTIMIZATION Configuring Backup Duplexing: CONFIGURE... BACKUP COPIES Showing the Configured Degree of Duplexing: SHOW... BACKUP COPIES Configuring Tablespaces for Exclusion from Whole Database Backups Showing the Tablespaces Excluded from Backups Configuring Auxiliary Instance Datafile Names: CONFIGURE AUXNAME Showing the Default Filenames Configured for Auxiliary Channels Setting the Snapshot Control File Location Default Location of the Snapshot Control File Viewing the Configured Location of the Snapshot Control File Setting the Location of the Snapshot Control File Showing the Current Snapshot Control File Name Setting Up RMAN for Use with a Shared Server Making Backups with RMAN: Advanced Topics Configuring and Allocating Channels for Use in Backups Duplexing Backup Sets Duplexing Backup Sets with CONFIGURE BACKUP COPIES Duplexing Backupsets with BACKUP... COPIES Making Split Mirror Backups with RMAN Backing Up Backup Sets with RMAN BACKUP BACKUPSET and Backup Retention Policy Backing Up Existing Image Copy Backups with RMAN RMAN Encrypted Backups RMAN Backup Encryption Modes Transparent Encryption of Backups Password Encryption of Backups vii

8 Dual Mode Encryption of Backups Using CONFIGURE and SET to Control RMAN Backup Encryption Creating Encrypted Backups Restoring Data from Encrypted Backups Encryption of Archived Log Backups Performance Impact of Encrypting RMAN Backups Restarting and Optimizing RMAN Backups Backing Up Files Using Backup Optimization Restarting a Backup After It Partially Completes Backups to CD, DVD and Other Disk Devices with Large Block Sizes Validating Backups with RMAN RMAN Backup Examples Skipping Tablespaces when Backing Up a Database: Example Restarting a Backup: Example Spreading a Backup Across Multiple Disk Drives: Example Specifying the Size of Backup Sets: Example Limiting the Size of Backup Pieces: Example Backing Up Archived Redo Logs in a Failover Scenario: Example Backing Up Archived Logs Needed to Recover an Online Backup: Example Backing Up and Deleting Multiple Copies of an Archived Redo Log: Example Determining How Channels Distribute a Backup Workload: Example Backing Up in NOARCHIVELOG Mode: Example Keeping a Long-Term Backup: Example Using Backup Optimization: Examples Optimizing a Database Backup: Example Optimizing a Daily Archived Log Backup to a Single Tape: Example Optimizing a Daily Archived Log Backup to Multiple Tapes: Example Creating a Weekly Secondary Backup of Archived Logs: Example Handling Corruption During Backups: Example Advanced RMAN Recovery Techniques Restore and Recovery of NOARCHIVELOG Databases Recovering a Database in NOARCHIVELOG Mode Using Incremental Backups Restore and Recovery of the Database on a New Host Preparing for Restore of a Database to a New Host Testing the Restore of a Database to a New Host: Scenario Performing Recovery with a Backup Control File Performing Recovery with a Backup Control File and No Recovery Catalog: Scenario Performing Disaster Recovery Performing Block Media Recovery with RMAN Block Media Recovery Using All Available Backups Block Media Recovery Using Specific Backups Block Media Recovery of Blocks Listed in V$DATABASE_BLOCK_CORRUPTION RMAN Restore and Recovery Examples Restoring Datafile Copies to a New Host: Example Restoring Control File When Databases in the Catalog Have the Same Name: Example Restoring a Backup Control File By Using the DBID viii

9 Recovering a Lost Datafile Without a Backup: Example RMAN Tablespace Point-in-Time Recovery (TSPITR) Understanding RMAN TSPITR RMAN TSPITR Concepts How TSPITR Works With an RMAN-Managed Auxiliary Instance Deciding When to Use TSPITR Limitations of TSPITR Planning and Preparing for TSPITR Choosing the Right Target Time for TSPITR Determining the Recovery Set: Analyzing Data Relationships Identifying and Resolving Dependencies on the Primary Database Identifying and Preserving Objects That Will Be Lost After TSPITR Performing Basic RMAN TSPITR Fully Automated RMAN TSPITR Using an Auxiliary Destination for Automated RMAN TSPITR Performing Fully Automated RMAN TSPITR Tasks to Perform After Successful TSPITR Handling Errors in Automated TSPITR Performing Customized RMAN TSPITR with an RMAN-Managed Auxiliary Instance Renaming TSPITR Recovery Set Datafiles with SET NEWNAME Renaming TSPITR Auxiliary Set Datafiles Renaming TSPITR Auxiliary Set Datafiles with SET NEWNAME Using DB_FILE_NAME_CONVERT to Name Auxiliary Set Datafiles Order of Precedence Among File Renaming Methods in TSPITR Specifying Auxiliary Instance Control File Location in TSPITR Specifying Auxiliary Instance Online Log Location in TSPITR Using Image Copies for Faster RMAN TSPITR Performance Using CONFIGURE AUXNAME With Recovery Set Image Copies in TSPITR SET NEWNAME and CONFIGURE AUXNAME With Auxiliary Set Image Copies Performing TSPITR With CONFIGURE AUXNAME and Image Copies: Scenario Customizing Initialization Parameters for the Automatic Auxiliary Instance in TSPITR Performing RMAN TSPITR Using Your Own Auxiliary Instance Preparing Your Own Auxiliary Instance for RMAN TSPITR Step 1: Create an Oracle Password File for the Auxiliary Instance Step 2: Create an Initialization Parameter File for the Auxiliary Instance Step 3: Check Oracle Net Connectivity to the Auxiliary Instance Preparing RMAN Commands for TSPITR with Your Own Auxiliary Instance Planning Channels for TSPITR with Your Own Auxiliary Instance Planning Datafile Names with Your Own Auxiliary Instance: SET NEWNAME Executing TSPITR with Your Own Auxiliary Instance Step 1: Start the Auxiliary Instance in NOMOUNT Mode Step 2: Connect the RMAN Client to Target and Auxiliary Instances Step 3: Execute the RECOVER TABLESPACE Command Executing TSPITR With Your Own Auxiliary Instance: Scenario Troubleshooting RMAN TSPITR Troubleshooting TSPITR: Filename Conflicts ix

10 Troubleshooting TSPITR: Insufficient Sort Space during Export Troubleshooting TSPITR: RMAN Cannot Identify Tablespaces with Undo Segments Troubleshooting: Restarting Manual Auxiliary Instance After TSPITR Failure RMAN Backup and Repository Maintenance RMAN Reporting Using the RMAN LIST Command RMAN Reports Reports of Obsolete Backups Crosschecks of RMAN Backups Deleting RMAN Backups Summary of RMAN Methods for Deleting Backups Removal of Backups with the DELETE Command Advantage of Using DELETE Instead of Operating System Commands Deletion of Obsolete Backups Deletion of Expired Backups Deletion of Archived Redo Logs That Are Already Backed Up Deletion of Files After Backup Using BACKUP... DELETE INPUT BACKUP... DELETE INPUT With Corrupt Archive Logs How RMAN Deletes Backup Records from the RMAN Repository Behavior of DELETE Command When the Repository and Media Do Not Correspond CHANGE... AVAILABLE and UNAVAILABLE with RMAN Backups Changing Retention Policy Status of RMAN Backups Monitoring RMAN Through V$ Views Correlating Server Sessions with RMAN Channels Matching Server Sessions with Channels When One RMAN Session Is Active Matching Server Sessions with Channels in Multiple RMAN Sessions Monitoring RMAN Job Progress Monitoring RMAN Interaction with the Media Manager Monitoring RMAN Job Performance Managing the Recovery Catalog Creating a Recovery Catalog Configuring the Recovery Catalog Database Planning the Size of the Recovery Catalog Schema Allocating Disk Space for the Recovery Catalog Database Creating the Recovery Catalog Owner Creating the Recovery Catalog Managing Target Database Records in the Recovery Catalog Registering a Database in the Recovery Catalog Cataloging Older Files in the Recovery Catalog Registering Multiple Databases in a Recovery Catalog Unregistering a Target Database from the Recovery Catalog Resetting the Database Incarnation in the Recovery Catalog Removing DELETED Records From the Recovery Catalog After Upgrade Resynchronizing the Recovery Catalog Types of Records Updated When Recovery Catalog is Resynchronized x

11 Full and Partial Resynchronization When to Resynchronize the Recovery Catalog Resynchronizing After the Recovery Catalog is Unavailable Resynchronizing in ARCHIVELOG Mode When You Back Up Infrequently Resynchronizing After Physical Database Changes Forcing a Full Resynchronization of the Recovery Catalog Resynchronizing the Recovery Catalog and CONTROL_FILE_RECORD_KEEP_TIME Managing the Control File When You Use a Recovery Catalog Working with RMAN Stored Scripts in the Recovery Catalog Creating Stored Scripts: CREATE SCRIPT Running Stored Scripts: EXECUTE SCRIPT Displaying a Stored Script: PRINT SCRIPT Listing Stored Scripts: LIST SCRIPT NAMES Updating Stored Scripts: REPLACE SCRIPT Deleting Stored Scripts: DELETE SCRIPT Starting the RMAN Client and Running a Stored Script Restrictions on Stored Script Names Backing Up and Recovering the Recovery Catalog Backing Up the Recovery Catalog Back Up the Recovery Catalog Often Choosing the Appropriate Method for Physical Backups Safe Storage of the Recovery Catalog Exporting the Recovery Catalog Data for Logical Backups Restoring and Recovering the Recovery Catalog from Backup Re-Creating the Recovery Catalog Exporting and Importing the Recovery Catalog Considerations When Moving Catalog Data Exporting the Recovery Catalog Importing the Recovery Catalog Increasing Availability of the Recovery Catalog Querying Recovery Catalog Views Identifying Rows for a Database in the Catalog Views Identifying Rows for a Database Object in the Catalog Views Querying Catalog Views for the Target DB_KEY or DBID Values Using RC_BACKUP_FILES and DBMS_RCVMAN.SETDATABASE Determining the Schema Version of the Recovery Catalog Upgrading the Recovery Catalog Dropping the Recovery Catalog Tuning Backup and Recovery Tuning Recovery Manager: Overview I/O Buffer Allocation Allocation for Disk Buffers Allocation of Tape Buffers Synchronous and Asynchronous I/O Synchronous I/O: Example Factors Affecting Backup Speed to Tape xi

12 Native Transfer Rate Tape Compression Tape Streaming Physical Tape Block Size Features and Options Used to Tune RMAN Performance Using the RATE Parameter to Control Disk Bandwidth Usage Tuning RMAN Backup Performance: Procedure Step 1: Remove RATE Parameters from Configured and Allocated Channels Step 2: If You Use Synchronous Disk I/O, Set DBWR_IO_SLAVES Step 3: If You Fail to Allocate Shared Memory, Set LARGE_POOL_SIZE Step 4: Tune RMAN Tape Streaming Performance Bottlenecks Using BACKUP... VALIDATE To Distinguish Between Tape and Disk Bottlenecks Using Multiplexing to Improve Tape Streaming with Disk Bottlenecks Using Incremental Backups to Improve Backup Performance With Tape Bottlenecks 11-7 Step 5: Query V$ Views to Identify Bottlenecks Identifying Bottlenecks with Synchronous I/O Identifying Bottlenecks with Asynchronous I/O Instance Recovery Performance Tuning: Fast-Start Fault Recovery Understanding Instance Recovery Cache Recovery (Rolling Forward) Transaction Recovery (Rolling Back) Checkpointing and Cache Recovery How Checkpoints Affect Performance Configuring the Duration of Cache Recovery: FAST_START_MTTR_TARGET Practical Values for FAST_START_MTTR_TARGET Reducing Checkpoint Frequency to Optimize Runtime Performance Monitoring Cache Recovery with V$INSTANCE_RECOVERY Tuning FAST_START_MTTR_TARGET and Using MTTR Advisor Calibrate the FAST_START_MTTR_TARGET Determine the Practical Range for FAST_START_MTTR_TARGET Evaluate Different Target Values with MTTR Advisor Determine Optimal Size for Redo Logs Recovery Manager Troubleshooting Interpreting RMAN Message Output Identifying Types of Message Output Recognizing RMAN Error Message Stacks Identifying Error Codes RMAN Error Message Numbers ORA-19511: Media Manager Errors Interpreting RMAN Error Stacks Interpreting RMAN Errors: Example Interpreting Server Errors: Example Interpreting SBT 2.0 Media Management Errors: Example Interpreting SBT 1.1 Media Management Errors: Example Identifying RMAN Return Codes Testing the Media Management API xii

13 Obtaining the sbttest Utility Obtaining Online Documentation for the sbttest Utility Using the sbttest Utility Terminating an RMAN Command Terminating the Session with ALTER SYSTEM KILL SESSION Terminating the Session at the Operating System Level Terminating an RMAN Session That Is Hung in the Media Manager Components of an RMAN Session Process Behavior During a Hung Job Terminating an RMAN Session: Basic Steps RMAN Troubleshooting Scenarios After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario After Installation of Media Manager, RMAN Channel Allocation Fails: Diagnosis After Installation of Media Manager, RMAN Channel Allocation Fails: Solution Backup Job Is Hanging: Scenario Backup Job Is Hanging: Diagnosis Backup Job Is Hanging: Solution RMAN Fails to Start RPC Call: Scenario RMAN Fails to Start RPC Call: Diagnosis Backup Fails with Invalid RECID Error: Scenario Backup Fails with Invalid RECID Error: Diagnosis Backup Fails with Invalid RECID Error: Solution Backup Fails with Invalid RECID Error: Solution Backup Fails Because of Control File Enqueue: Scenario Backup Fails Because of Control File Enqueue: Diagnosis Backup Fails Because of Control File Enqueue: Solution RMAN Fails to Delete All Archived Logs: Scenario RMAN Fails to Delete All Archived Logs: Diagnosis RMAN Fails to Delete All Archived Logs: Solution Backup Fails Because RMAN Cannot Locate an Archived Log: Scenario Backup Fails Because RMAN Cannot Locate an Archived Log: Diagnosis Backup Fails Because RMAN Cannot Locate an Archived Log: Solution RMAN Does Not Recognize Character Set Name: Scenario RMAN Does Not Recognize Character Set Name: Diagnosis RMAN Does Not Recognize Character Set Name: Solution RMAN Denies Logon to Target Database: Scenario RMAN Denies Logon to Target Database: Diagnosis RMAN Denies Logon to Target Database: Solution Database Duplication Fails Because of Missing Log: Scenario Database Duplication Fails Because of Missing Log: Diagnosis Database Duplication Fails Because of Missing Log: Solution Duplication Fails with Multiple RMAN Errors: Scenario Duplication Fails with Multiple RMAN Errors: Diagnosis Duplication Fails with Multiple RMAN Errors: Solution UNKNOWN Database Name Appears in Recovery Catalog: Scenario UNKNOWN Database Name Appears in Recovery Catalog: Diagnosis UNKNOWN Database Name Appears in Recovery Catalog: Solution xiii

14 Part III Using RMAN for Database Transport, Duplication and Migration 13 Creating and Updating Duplicate Databases with RMAN Creating a Duplicate Database with RMAN: Overview How Recovery Manager Duplicates a Database RMAN DUPLICATE DATABASE: Options RMAN DUPLICATE DATABASE: Prerequisites and Restrictions Renaming Database Files in RMAN Duplicate Database Renaming Control Files in RMAN DUPLICATE DATABASE Renaming Online Logs in RMAN DUPLICATE DATABASE Renaming Datafiles in RMAN DUPLICATE DATABASE Preventing Filename Checking when Duplicating a Database Renaming Tempfiles in RMAN DUPLICATE DATABASE Skipping Tablespaces in RMAN DUPLICATE DATABASE Skipping Read-Only Tablespaces When Duplicating a Database Skipping OFFLINE NORMAL Tablespaces When Duplicating a Database Preparing the RMAN DUPLICATE Auxiliary Instance: Basic Steps Task 1: Create an Oracle Password File for the Auxiliary Instance Task 2: Establish Oracle Net Connectivity to the Auxiliary Instance Task 3: Create an Initialization Parameter File for the Auxiliary Instance Task 4: Start the Auxiliary Instance Task 5: Mount or Open the Target Database Task 6: Make Sure You Have the Necessary Backups and Archived Redo Logs Task 7: Allocate Auxiliary Channels if Automatic Channels Are Not Configured 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 Converting Filenames with Only Initialization Parameters Converting Filenames with Only DUPLICATE Parameters Using RMAN DUPLICATE With SET NEWNAME: Example Using RMAN DUPLICATE With CONFIGURE AUXNAME: Example Creating a Duplicate Database on the Local Host Using RMAN DUPLICATE with OMF and ASM Initialization Parameters for RMAN DUPLICATE to OMF Storage Duplicating a Database to ASM Storage Using SET NEWNAME with RMAN DUPLICATE to OMF Using RMAN DUPLICATE DATABASE: Examples Duplicating When the Datafiles Use Inconsistent Paths: Example RMAN DUPLICATE DATABASE From File System to ASM: Example RMAN DUPLICATE DATABASE From ASM to ASM: Example RMAN DUPLICATE DATABASE at a Past Point in Time: Example Duplicating with a Client-Side Parameter File: Example Running RMAN Client on host_dup Running RMAN from host_src Using DUPLICATE DATABASE to Resynchronize a Duplicate Database: Example Using CONFIGURE AUXNAME to Name Datafiles at the Duplicate Syncrhonizing the Duplicate With the Target Using Auxnames xiv

15 Using RMAN Incremental Backups to Refresh a Standby Database Using BACKUP INCREMENTAL... FROM SCN Refreshing a Standby Database With INCREMENTAL FROM SCN Backups: Example Step 1: Create the Incremental Backup Step 2: Make the Incremental Backup Accessible at the Standby Database Step 3: Catalog the Incremental Backup Files at the Standby Database Step 4: Apply the Incremental Backup to the Standby Database Creating Transportable Tablespace Sets from Backup with RMAN About Creating Transportable Tablespace Sets from Backup with RMAN Transportable Tablespace Sets from Backup: Concepts When to Use RMAN to Create Transportable Tablespace Sets How RMAN Creates Transportable Tablespace Sets from Backup Steps RMAN Performs in Transporting Tablespaces from Backup Limitations of RMAN TRANSPORT TABLESPACE Command Creating a Transportable Tablespace Set with RMAN: Procedure Using RMAN TRANSPORT TABLESPACE: Basic Scenario RMAN TRANSPORT TABLESPACE with UNTIL Time or SCN RMAN TRANSPORT TABLESPACE: Specifying Locations for Data Pump Files RMAN TRANSPORT TABLESPACE with Customized Initialization Parameters RMAN TRANSPORT TABLESPACE Default Auxiliary Instance Parameters Location of the Auxiliary Instance Parameter File Using an Auxiliary Instance Parameter File: Example Customize Shared Pool Size in RMAN TRANSPORT TABLESPACE Customize Auxiliary Control File Location in TRANSPORT TABLESPACE Customize Other Auxiliary File Locations in TRANSPORT TABLESPACE Transport Tablespace with SET NEWNAME for Auxiliary Datafiles Transport Tablespace with CONFIGURE AUXNAME for Auxiliary Datafiles Transport Tablespace with AUXILIARY DESTINATION Parameter Transport Tablespace and Naming Auxiliary Files with Initialization Parameters Troubleshooting RMAN TRANSPORT TABLESPACE Troubleshooting RMAN TRANSPORT TABLESPACE: Insufficient Shared Pool Troubleshooting RMAN TRANSPORT TABLESPACE: Filename Conflicts RMAN Cross-Platform Transportable Databases and Tablespaces Cross-Platform Tranportable Tablespace: CONVERT DATAFILE or TABLESPACE Using CONVERT TABLESPACE... TO PLATFORM on the Source Platform Rules for Renaming Files with CONVERT TABLESPACE Converting Tablespaces on the Source Host: Example Using CONVERT DATAFILE... FROM PLATFORM on the Destination Host Converting Datafiles on the Destination Platform: Example Restrictions on CONVERT TABLESPACE and CONVERT DATAFILE Cross-Platform Transportable Database: RMAN CONVERT DATABASE Restrictions on Cross-Platform Transportable Database Performing Cross-Platform Database Transport Preparing for CONVERT DATABASE: Using the DBMS_TDB Package xv

16 Using DBMS_TDB.CHECK_DB to Check Database State Using DBMS_TDB.CHECK_EXTERNAL to Identify External Objects Using the RMAN CONVERT DATABASE Command CONVERT DATABASE, Converting Datafiles on the Source Platform CONVERT DATABASE. Converting Datafiles on the Destination Host Using RMAN CONVERT to Copy Files Between ASM and Non-ASM Storage Copying Datafiles To ASM Using CONVERT DATAFILE: Example Copying Datafiles From ASM Using CONVERT DATAFILE: Example Copying Tablespaces From ASM With CONVERT TABLESPACE: Example Migrating Databases To and From ASM with Recovery Manager Migrating a Database into ASM Limitation on ASM Migration with Transportable Tablespaces Preparing to Migrate a Database to ASM Determine Names of Database Files Generate RMAN Command File to Undo ASM Migration Disk-Based Migration of a Database to ASM Migrating the Flash Recovery Area to ASM Setting Initialization Parameters for Flash Recovery Area in ASM Migrating the Control File to an ASM Flash Recovery Area Changing Flashback Log Location to ASM Flash Recovery Area Migrating Online Logs to ASM Flash Recovery Area Migrating Existing Backups to ASM Flash Recovery Area Migrating a Database from ASM to Non-ASM Storage PL/SQL Scripts Used in Migrating to ASM Storage Generating ASM-to-Non-ASM Storage Migration Script Migrating Online Logs of Primary Database to ASM Part IV Performing User-Managed Backup and Recovery 17 Making User-Managed Backups Querying V$ Views to Obtain Backup Information Listing Database Files Before a Backup Determining Datafile Status for Online Tablespace Backups Making User-Managed Backups of the Whole Database Making Consistent Whole Database Backups Making User-Managed Backups of Offline Tablespaces and Datafiles Making User-Managed Backups of Online Tablespaces and Datafiles Making User-Managed Backups of Online Read/Write Tablespaces Making Multiple User-Managed Backups of Online Read/Write Tablespaces Backing Up Online Tablespaces in Parallel Backing Up Online Tablespaces Serially Ending a Backup After an Instance Failure or SHUTDOWN ABORT Ending Backup Mode with the ALTER DATABASE END BACKUP Statement Ending Backup Mode with the SQL*Plus RECOVER Command Making User-Managed Backups of Read-Only Tablespaces xvi

17 Making User-Managed Backups of the Control File Backing Up the Control File to a Binary File Backing Up the Control File to a Trace File Backing Up the Control File to a Trace File: Example Making User-Managed Backups of Archived Redo Logs Making User-Managed Backups in SUSPEND Mode About the Suspend/Resume Feature Making Backups in a Suspended Database Making User-Managed Backups to Raw Devices Backing Up to Raw Devices on UNIX Backing Up with the dd utility on UNIX: Examples Backing Up to Raw Devices on Windows Backing Up with OCOPY: Example Specifying the -b and -r Options for OCOPY: Example Verifying User-Managed Backups Testing the Restore of Backups Running the DBVERIFY Utility Making Logical Backups with Oracle Export Utilities Making User-Managed Backups of Miscellaneous Oracle Files Keeping Records of Current and Backup Database Files Recording the Locations of Datafiles, Control Files, and Online Redo Logs Recording the Locations of Archived Redo Logs Recording the Locations and Dates of Backup Files Performing User-Managed Database Flashback and Recovery User-Managed Flashback Features of Oracle Performing Flashback Database with SQL*Plus About User-Managed Restore Operations Determining Which Datafiles Require Recovery Restoring Datafiles and Archived Redo Logs Restoring Datafiles with Operating System Utilities Restoring Archived Redo Logs with Operating System Utilities Restoring Control Files Restore Lost Copy of a Multiplexed Control File Copying a Multiplexed Control File to a Default Location Copying a Multiplexed Control File to a Nondefault Location Restore Control File from Backup After Loss of All Current Control Files Restoring a Backup Control File to the Default Location Restoring a Backup Control File to a Nondefault Location Create New Control File After Losing All Current and Backup Control Files About User-Managed Media Recovery Preconditions of Performing User-Managed Recovery Applying Logs Automatically with the RECOVER Command Automating Recovery with SET AUTORECOVERY Automating Recovery with the AUTOMATIC Option of the RECOVER Command Recovering When Archived Logs Are in the Default Location Recovering When Archived Logs Are in a Nondefault Location xvii

18 Resetting the Archived Log Destination Overriding the Archived Log Destination Responding to Unsuccessful Application of Redo Logs Interrupting User-Managed Media Recovery Performing Complete User-Managed Media Recovery Performing Closed Database Recovery Preparing for Closed Database Recovery Restoring Backups of the Damaged or Missing Files Recovering the Database Performing Datafile Recovery in an Open Database Preparing for Open Database Recovery Restoring Backups of the Inaccessible Datafiles Recovering Offline Tablespaces in an Open Database Performing User-Managed Database Point-in-Time Recovery Preparing for Incomplete Recovery Restoring Datafiles Before Performing Incomplete Recovery Performing Cancel-Based Incomplete Recovery Performing Time-Based or Change-Based Incomplete Recovery Opening the Database with the RESETLOGS Option About Opening with the RESETLOGS Option Executing the ALTER DATABASE OPEN Statements Checking the Alert Log After a RESETLOGS Operation Recovering a Database in NOARCHIVELOG Mode Restoring a NOARCHIVELOG Database to its Default Location Restoring a NOARCHIVELOG Database to a New Location Controlling Parallel Media Recovery Advanced User-Managed Recovery Scenarios Recovering After the Loss of Datafiles: Scenarios Losing Datafiles in NOARCHIVELOG Mode Losing Datafiles in ARCHIVELOG Mode Recovering Through an Added Datafile with a Backup Control File: Scenario Re-Creating Datafiles When Backups Are Unavailable: Scenario Recovering Through RESETLOGS with Created Control File: Scenario Recovering NOLOGGING Tables and Indexes: Scenario Recovering Read-Only Tablespaces with a Backup Control File: Scenario Recovery of Read-Only or Slow Media with a Backup Control File Recovery of Read-Only Files with a Re-Created Control File Media Recovery of Transportable Tablespaces: Scenario Recovering After the Loss of Online Redo Log Files: Scenarios Recovering After Losing a Member of a Multiplexed Online Redo Log Group Recovering After the Loss of All Members of an Online Redo Log Group Losing an Inactive Online Redo Log Group Losing an Active Online Redo Log Group Loss of Multiple Redo Log Groups Recovering After the Loss of Archived Redo Log Files: Scenario Recovering from a Dropped Table: Scenario xviii

19 Performing Media Recovery in a Distributed Environment: Scenario Coordinating Time-Based and Change-Based Distributed Database Recovery Dropping a Database with SQL*Plus Performing User-Managed TSPITR Introduction to User-Managed Tablespace Point-in-Time Recovery TSPITR Terminology TSPITR Methods Preparing for User-Managed Tablespace Point-in-Time Recovery: Basic Steps Step 1: Review TSPITR Requirements Step 2: Identify All of the Files in the Recovery and Auxiliary Set Tablespaces Step 3: Determine Whether Objects Will Be Lost Step 4: Choose a Method for Connecting to the Auxiliary Instance Step 5: Create an Oracle Password File for the Auxiliary Instance Step 6: Create the Initialization Parameter File for the Auxiliary Instance Restoring and Recovering the Auxiliary Databas in User-Managed TSPITR: Basic Steps Restoring and Recovering the Auxiliary Database on the Same Host Restoring the Auxiliary Database on a Different Host with the Same Path Names Restoring the Auxiliary Database on a Different Host with Different Path Names Performing User-Managed TSPITR with Transportable Tablespaces Step 1: Unplugging the Tablespaces from the Auxiliary Database Step 2: Transporting the Tablespaces into the Primary Database Performing Partial TSPITR of Partitioned Tables Step 1: Create a Table on the Primary Database for Each Partition Being Recovered Step 2: Drop the Indexes on the Partition Being Recovered Step 3: Exchange Partitions with Standalone Tables Step 4: Drop the Recovery Set Tablespace Step 5: Create Tables at Auxiliary Database Step 6: Drop Indexes on Partitions Being Recovered Step 7: Exchange Partitions with Standalone Tables on the Auxiliary Database Step 8: Transport the Recovery Set Tablespaces Step 9: Exchange Partitions with Standalone Tables on the Primary Database Step 10: Back Up the Recovered Tablespaces in the Primary Database Performing User-Managed TSPITR of Partitioned Tables With a Dropped Partition Step 1: Find the Low and High Range of the Partition that Was Dropped Step 2: Create a Temporary Table Step 3: Delete Records From the Partitioned Table Step 4: Drop the Recovery Set Tablespace Step 5: Create Tables at the Auxiliary Database Step 6: Drop Indexes on Partitions Being Recovered Step 7: Exchange Partitions with Standalone Tables Step 8: Transport the Recovery Set Tablespaces Step 9: Insert Standalone Tables into Partitioned Tables Step 10: Back Up the Recovered Tablespaces in the Primary Database Performing User-Managed TSPITR of Partitioned Tables When a Partition Has Split Step 1: Drop the Lower of the Two Partitions at the Primary Database Steps 2: Follow Same Procedure as for Partial TSPITR of Partitioned Tablespaces xix

20 21 Troubleshooting User-Managed Media Recovery Index About User-Managed Media Recovery Problems Investigating the Media Recovery Problem: Phase Trying to Fix the Recovery Problem Without Corrupting Blocks: Phase Deciding Whether to Allow Recovery to Corrupt Blocks: Phase Allowing Recovery to Corrupt Blocks: Phase Performing Trial Recovery How Trial Recovery Works Executing the RECOVER... TEST Statement xx

21 Preface This preface contains these topics: Audience Documentation Accessibility Related Documentation Conventions Audience Backup and Recovery Advanced User s Guide is intended for database administrators who perform the following tasks: Back up, restore, and recover Oracle databases Perform maintenance on backups of database files To use this document, you need to know the following: Relational database concepts and basic database administration as described in Oracle Database Concepts and the Oracle Database Administrator's Guide Basic backup and recovery concepts and strategies as described in Oracle Database Backup and Recovery Basics The operating system environment under which you are running the database 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 documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility 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 more information, visit the Oracle Accessibility Program Web site at Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an xxi

22 otherwise empty line; however, some screen readers 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 organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites. TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call Related Documentation For more information, see these Oracle resources: Oracle Database Backup and Recovery Basics Oracle Database Backup and Recovery Reference Oracle Database Utilities You can access information about the Backup Solutions Program at Many books in the documentation set use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself. Oracle error message documentation is only available in HTML. If you only have access to the Oracle Documentation CD, you can browse the error messages by range. Once you find the specific range, use your browser's "find in page" feature to locate the specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation. Conventions The following text conventions are used in this document: Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. xxii