Oracle Support Master Note For Oracle Recovery Manager (RMAN) (Doc ID 1116484.1)

+++++++++++++++++++++++++++++++++++++++++++++++++++++
The complete and recent article can be accessed from
My Oracle Support Knowledge Section.

Master Note For Oracle Recovery Manager (RMAN) (Doc ID 1116484.1)
+++++++++++++++++++++++++++++++++++++++++++++++++++++

In this Document
  Purpose
  Scope and Application
  Master Note For Oracle Recovery Manager (RMAN)
     Getting started with RMAN
     Rman compatibility
     Flash Recovery Area
     Configuring the environment for RMAN backups
     Recovery catalog for RMAN backups.
     Backing up database files using RMAN and maintenance of backup records.
     Restore and recovery techniques/scenarios using RMAN
     Tablespace point in time recovery
     RMAN Transportable tablespace and database
     RMAN Duplicate database
     RMAN Performance
     RMAN and Media managers
     Rman and Dataguard
     Rman and RAC
     Rman and Corruption
     Related Master Notes
     Using My Oracle Support Effectively
     Generic Links




Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.2.0.1.0 - Release: 10.1 to 11.2
Information in this document applies to any platform.

Purpose

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support Notes with respect to Oracle Recovery Manager (RMAN).This Master Note is subdivided into categories to allow for easy access and reference to notes that are applicable to your area of interest, within RMAN.This includes the following categories:

  • Getting started with RMAN
  • Rman compatibility
  • Flash Recovery Area
  • Configuring the environment for RMAN backups
  • Recovery catalog for RMAN backups
  • Backing up database files using RMAN and maintaining the backup records
  • Restore and recovery techniques/scenarios using RMAN
  • Tablespace point in time recovery (TSPITR)
  • RMAN Transportable tablespaces and database
  • RMAN Duplicate database
  • RMAN Performance.
  • RMAN and Media managers.
  • RMAN and Dataguard
  • RMAN and Rac
  • RMAN and Corruption
  • Related Master Notes
  • Using My Oracle Support Effectively
  • Generic Links

Scope and Application

Recovery Manager is Oracle's utility to manage the backup, and more importantly the recovery, of the database. It eliminates operational complexity while providing superior performance and availability of the database. Recovery Manager debuted with Oracle8 to provide DBAs an integrated backup and recovery solution.

Recovery Manager determines the most efficient method of executing the requested backup, restore, or recovery operation and then executes these operations in concert with the Oracle database server. Recovery Manager and the server automatically identify modifications to the structure of the database and dynamically adjust the required operation to adapt to the changes.

This note applies to the following versions of these products:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.x
Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.x
Oracle Server - Enterprise Edition - Version: 11.2.0.1 to 11.2.0.x

Master Note For Oracle Recovery Manager (RMAN)

Getting started with RMAN

The articles in this section give you a overview of the oracle utility RMAN,the new features of RMAN in Oracle 11 release 1,2 and FAQ on RMAN.

Note.360416.1    Oracle10g / 11g - Getting Started with Recovery Manager (RMAN)
Note 809867.1    RMAN 11gR1 : New Features
Note 1115423.1   Rman Enhancements In Oracle 11g.
Note.469777.1    RMAN - Frequently Asked Question (FAQ)

Rman compatibility

Note.73431.1 RMAN Compatibility Matrix

Flash Recovery Area

The flash recovery area is an Oracle-managed directory, file system, or Automatic Storage Management disk group that provides a centralized disk location for backup and recovery files. All the files you need to completely recover a database from a media failure are part of the Flash Recovery Area. Oracle creates archived logs and flashback logs in the flash recovery area. RMAN can store its backup sets and image copies in the flash recovery area, and it uses it when restoring files during media recovery. The flash recovery area also acts as a disk cache for tape.

The articles mentioned in the following section help you in understanding the concepts and working of flash recovery area,Rman integration with the flash recovery area and troubleshooting flash recovery area issues.

Note.305648.1  What is a Flash Recovery Area and how to configure it ?
Note.305796.1  RMAN and Flash Recovery Area
Note.833663.1  Flash Recovery Area - FAQ
Note.560133.1  Benefits Of Using Flash Recovery Area
Note.315098.1  How is the space pressure managed in the Flash Recovery Area - An Example.
Note.305812.1  Flash Recovery area - Space management Warning & Alerts
Note.829755.1  Space issue in Flash Recovery Area( FRA )
Note.305810.1  Configuring file creation in Flash recovery area and order of Precedence
Note.305651.1  How to change Flash Recovery Area to a new location ?
Note.762934.1  Flash Recovery Area Sizing

Configuring the environment for RMAN backups

To simplify ongoing use of RMAN, you can set a number of persistent configuration settings for each target database. These settings control many aspects of RMAN behavior. For example, you can configure the backup retention policy, default destinations for backups, default backup device type, and so on. You can use the SHOW and CONFIGURE commands to view and change RMAN configurations.

The articles mentioned in the following section help you in configuring the rman persistent configurations,understanding their behaviour and troubleshooting them.

Note 305565.1  Persistent Controlfile Configurations for RMAN in 9i and 10g
Note.462978.1  Rman backup retention policy
Note.463875.1  Frequently asked questions on Rman backup retention policy
Note.351455.1  Oracle Suggested Strategy & Backup Retention

Recovery catalog for RMAN backups.

A recovery catalog is a set of tables and views that Recovery Manager (RMAN) uses to store metadata (information about a database structure, archived redo logs, backup sets, and data file copies) about a target database (database that RMAN backups or restores). RMAN uses this metadata to conduct its backup, recovery, and maintenance operations. Recovery catalog is optional, i.e., if a recovery catalog is not created, RMAN uses the target database's control file to store the metadata about the target database. Although RMAN can conduct all major backup and recovery operations by using the control file, some RMAN commands work only if a recovery catalog exists.

The articles in the following section describe the configuration,management of recovery catalog and some of the known issues related to recovery catalog.

Note.452529.1  Recovery catalog for RMAN backup
Note.467969.1  How To Configure RMAN Recovery Catalog Using Enterprise Manager DB Console.

Backing up database files using RMAN and maintenance of backup records.

The articles and links in the following section describe the different methods to perform backups and useful rman backup methods.

Oracle Database Backup and Recovery Advanced User's Guide

NOTE:388422.1  Top 10 Backup and Recovery best practices
Note 262853.1  10G RMAN Fast Incremental Backups
Note.745798.1  Merged Incremental Backup Strategies
Note.735953.1  How To Configure RMAN Backups To Tape via Oracle Enterprise Managery
@Note.550082.1 HOW TO CATALOG TAPE BACKUP PIECES
Note.137181.1  RMAN Backup Shell Script Example

Restore and recovery techniques/scenarios using RMAN

The articles in this section provide various restore and recovery techniques and scenarios what can be achieved using rman.

NOTE:388422.1   Top 10 Backup and Recovery best practices
Note.94114.1    Backup and Recovery Scenarios
Note.372996.1   Using RMAN to Restore and Recover a Database When Repository and Spfile/Init.ora Files Are Lost
Note.162855.1   RMAN Consistent Backup, Restore and Recovery using RMAN
@Note.416972.1  How to recover the whole database from media failure while RMAN database backup is available and
no recovery catalog?
Note.223543.1   How to Recover From a DROP / TRUNCATE / DELETE TABLE with RMAN
Note.144911.1   RMAN 9i Block-Level Media Recovery - Concept & Example
Note.403883.1   How To Restore Controlfile From A Backupset Without A Catalog Or Autobackup
Note.580414.1   RMAN - How to restore the controlfile using RMAN
Note.419137.1   How To Restore Rman Backups On A Different Node When The Directory Structures Are Different
Note.415579.1   How To Restore RMAN Disk backups of RAC Database to Single Instance On Another Node
Note.472536.1   10g RMAN Benefits of Simplified Recovery Through Resetlogs.
Note.61994.1    Procedures/Restrictions for Point-In-Time Recovery without a Recovery Catalog
Note.246325.1   Automated File Creation During RMAN Recovery
Note.358171.1   Oracle10g RMAN will not restore in parallel from tape

Tablespace point in time recovery

Recovery Manager (RMAN) Automatic TSPITR enables quick recovery of one or more tablespaces in a database to an earlier time without affecting the rest of the tablespaces and objects in the database.Here are a few articles which explain the steps involved in performing a TSPITR:

Note.109979.1  RMAN Tablespace Point In Time Recovery (TSPITR) Procedure.
Note.62332.1   TSPITR - An Example Walkthrough

RMAN Transportable tablespace and database

Rman can be used to create transportable tablespace sets and can be used to convert the datafiles for cross platform transportable tablespace and database. Here are a few articles which provide all the required information to understand the procedures:

Note.371556.1  How move tablespaces across platforms using Transportable Tablespaces with RMAN
Note.455593.1  Creating a transportable tablespace set from RMAN backupsets
Note.831223.1  Using Rman Incremental backups To Update Transportable Tablespaces.
Note.413586.1  How To Use RMAN CONVERT DATABASE on Source Host for Cross Platform Migration
Note.414878.1  Cross-Platform Migration on Destination Host Using Rman Convert Database
Note.733205.1  Migration of Oracle Database Instances Across OS Platforms

RMAN Duplicate database

Database duplication is the use of the DUPLICATE command to copy all or a subset of the data in a source database. The duplicate database (the copied database) functions entirely independently from the source database (the database being copied).In articles in this section help you in understanding the duplicate procedures and various techniques available for the rman duplicate operation.

Note.228257.1  RMAN 'Duplicate Database' Feature in Oracle9i / 10G and 11G
Note.452868.1  RMAN 'Duplicate Database' Feature in 11G
Note.1113713.1 Creation Of Rman Duplicate Without Target And Recovery Catalog Connection.
Note.388431.1  Creating a Duplicate Database on a New Host.
Note.382669.1  Duplicate database from non ASM to ASM (vise versa) to a different host
Note.388424.1  How To Create A Production (Full or Partial) Duplicate On The Same Host
Note.293717.1  How to duplicate a database to previous incarnation
Note.340848.1  Performing duplicate database with ASM/OMF/RMAN
Note 461479.1  RMAN Duplicate Database From RAC ASM To RAC ASM
Note.840647.1  Article on How to do Rman Duplicate on ASM/RAC/OMF/Single Instance
Note.360962.1  Manual Completion of a Failed RMAN Duplicate
Note.369644.1  Answers To FAQ For Restoring Or Duplicating Between Different Versions And Platforms

RMAN Performance

Note.360443.1  RMAN Backup Performance
Note 740911.1  RMAN Restore Performance
Note 247611.1  Known RMAN Performance Problems
NOTE.360443.1  Analyzing RMAN Performance Issues
NOTE.579158.1  Advise On How To Improve Rman Performance
NOTE.296985.1  RMAN Performance Data Gathering
Note.463227.1  Oracle10g RMAN Recovery Catalog Known Performance Issues

RMAN and Media managers

Oracle designed an architecture that allows RMAN to manage the process of database backup and recovery, yet integrate with industry-leading tape storage management subsystems. The interface between Rman and media management vendor products is keyed on an Oracle design specification. This specification allows Oracle RMAN to use third party media management software to back-up to and restore from tape.

Many organizations rely on Oracle to provide solutions for very large or highly distributed mission critical systems. In addition to needing databases capable of handling large amounts of data and complex queries, these organizations also need robust backup and recovery technology. Recovery of data quickly and reliably is paramount should some aspect of the system fail. To address these needs, Oracle has created the Backup Solutions Program (BSP), a cooperative program designed to facilitate tighter integration between Oracle's backup products and those of third-party media management vendors. Together, Oracle and media management vendors provide robust easy-to-use database backup and recovery solutions to customers with high-end requirements.

The link to access the information regarding backup solutions program is:


"Under the BSP, vendors are committed to integrating Recovery Manager (RMAN) with their media management software packages and provide first line technical support for the integrated backup and recovery solutions for Oracle RDBMS."

So any issues related to the media manager functionality or configuration has to be addressed only by the vendors and not by Oracle.

Below are a few articles which help you in understanding the most common issues with rman backups to tape, environment variable used for backups to tape and procedure to check if the media manager installation has been done properly.

Note.942418.1  How To Verify A Media Manager Layer Installation ?
Note 1062824.6 RMAN: Unable to Backup with Third-Party Storage Manager
Note.412950.1  How to determine if an RMAN failure or hang lies in the Media Manager Layer or not
Note 227517.1  Main Index of Common Causes for ORA-19511
NOTE.312737.1  RMAN and Specific Media Managers Environment Variables.

Rman and Dataguard

Data Guard and RMAN were both designed with the Oracle database architecture in mind. Together, they offer the most reliable and tightly integrated solution to achieve superior levels of Oracle database availability supporting your mission critical applications. Data Guard and RMAN are both fully supported features of the Oracle Database Enterprise Edition (RMAN is also provided with Oracle Database Standard Edition).Here are a few articles that help you in effectively using rman with dataguard and some of the known rman issues with dataguard.

Note.848716.1  Using RMAN Effectively In A Dataguard Environment
Note.357759.1  Known RMAN - Dataguard Problems
Note.368336.1  10gR1 RAC/DataGuard/ASM physical standby deployment procedure

Rman and RAC

Here are a few articles which will provide all the necessary information about how RMAN can be used in a RAC environment.

Note 243760.1  RMAN: RAC Backup and Recovery using RMAN
Note.415579.1  How To Restore RMAN Disk backups of RAC Database to Single Instance On Another Node
Note 461479.1  RMAN Duplicate Database From RAC ASM To RAC ASM
Note.840647.1  Article on How to do Rman Duplicate on ASM/RAC/OMF/Single Instance

Rman and Corruption

Rman is a very effective utility in identifying the database block corruption. Here are are a few article which provides the information about using rman to detect and fix corruption.

Note.283053.1  How To Use RMAN To Check For Logical & Physical Database Corruption
Note 836658.1  Identify the corruption extension using RMAN/DBV/ANALYZE etc
Note.561010.1  Which Blocks Will RMAN Check For Corruption Or Include In A Backupset?
Note 428570.1  Best Practices for Avoiding and Detecting Corruption

Related Master Notes

Note 1096952.1  Master Note for Real Application Clusters (RAC) Oracle Clusterware and Oracle Grid Infrastructure
Note 1088018.1  Master Note for Oracle Database Corruption
Note.1101938.1  Master Note for Data Guard

Using My Oracle Support Effectively

Note 374370.1  New Customers Start Here
Note 736737.1  My Oracle Support - The Next Generation Support Platform
Note 730283.1  Get the most out of My Oracle Support
Note 747242.5  My Oracle Support Configuration Management FAQ
Note 868955.1  My Oracle Support Health Checks Catalog
Note 166650.1  Working Effectively With Global Customer Support
Note 199389.1  Escalating Service Requests with Oracle Support Services

Generic Links

Note 854428.1  Patch Set Updates for Oracle Products
Note 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution
Note 881382.1  Critical Patch Update October 2009 Patch Availability Document for Oracle Products
Note 967472.1  Critical Patch Update January 2010 Patch Availability Document for Oracle Products
Note 1060989.1 Critical Patch Update April 2010 Patch Availability Document for Oracle Products
Note 756671.1  Oracle Recommended Patches -- Oracle Database
Note 268895.1  Oracle Database Server Patchset Information, Versions: 8.1. 7 to 11.2.0
Note 161549.1  Oracle Database Server and Networking Patches for Microsoft Platforms
Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

News and Troubleshooting tips for Oracle Database and Enterprise Manager

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today