Friday, August 12, 2022
RMAN DUPLICATE STANDBY
Wednesday, March 2, 2022
Script to monitor RMAN progress
Question: I have a long running RMAN job, and I want a script to monitor the progress of RMAN execution. How do you monitor RMAN progress?
Answer: Oracle has several views that can monitor long running jobs, including v$session_longops and v$process with v$session. Also see RMAN backup scripts from Windows DOS scripts for RMAN automated backups and example of RMAN shell script.
sselect
sid,
start_time,
totalwork
sofar,
(sofar/totalwork) * 100 pct_done
from
v$session_longops
where
totalwork > sofar
AND
opname NOT LIKE '%aggregate%'
AND
opname like 'RMAN%';select
sid,
spid,
client_info,
event,
seconds_in_wait,
p1, p2, p3
from
v$process p,
v$session s
where
p.addr = s.paddr
and
client_info like 'rman channel=%';
Yousef Rifai has published this RMAN monitoring script, quite handy when you need to monitor the status of a long running RMAN backup job:
REM RMAN Progress
alter session set nls_date_format='dd/mm/yy hh24:mi:ss'
/
select SID, START_TIME,TOTALWORK, sofar, (sofar/totalwork) * 100 done,
sysdate + TIME_REMAINING/3600/24 end_at
from v$session_longops
where totalwork > sofar
AND opname NOT LIKE '%aggregate%'
AND opname like 'RMAN%'
/
REM RMAN wiats
set lines 120
column sid format 9999
column spid format 99999
column client_info format a25
column event format a30
column secs format 9999
SELECT SID, SPID, CLIENT_INFO, event, seconds_in_wait secs, p1, p2, p3
FROM V$PROCESS p, V$SESSION s
WHERE p.ADDR = s.PADDR
and CLIENT_INFO like 'rman channel=%'
/
This script by Osama Mustafa will monitor the progress of a running RMAN job:
select
to_char(start_time,'DD-MON-YY HH24:MI') "BACKUP STARTED",
sofar,
totalwork,
elapsed_seconds/60 "ELAPSE (Min)",
round(sofar/totalwork*100,2) "Complete%"
from
sys.v_$session_longops
where compnam = 'dbms_backup_restore';
Thursday, July 15, 2021
Data Guard Physical Standby - Converting a Snapshot Standby back to a Physical Standby using Data Guard Broker (Doc ID 1546657.1)
this Document
| Goal |
| Solution |
| References |
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
GOAL
***Checked for relevance on 20-Oct-2016***
Perform a conversion of a Snapshot Standby database back to a Physical Standby Database.
Perform checks relevant to a successful conversion.
Monitor the conversion process to ensure that it has been executed correctly without error.
SOLUTION
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Primary database name: rs1_stb
Standby/Snapshot database name : rs1
Diskgroup : +DATA ,+FRA
The current configuration
The Primary Site
SQL*Plus: Release 11.2.0.3.0 Production on Thu Apr 18 11:58:26 2013
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> select db_unique_name,database_role,open_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE
------------------------------ ---------------- --------------------
rs1_stb PRIMARY READ WRITE
The Standby Site
SQL*Plus: Release 11.2.0.3.0 Production on Thu Apr 18 11:50:31 2013
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> select db_unique_name,database_role,open_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE
------------------------------ ---------------- --------------------
rs1 SNAPSHOT STANDBY READ WRITE
Checks to perform prior to the conversion
1. Check from a Data Guard Broker perspective the configuration is healthy and the configuration status is reported as "SUCCESS".
DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys@rs1_stb
Password:
Connected.
DGMGRL> show configuration;
Configuration - rs1_dg
Protection Mode: MaxPerformance
Databases:
rs1_stb - Primary database
rs1 - Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
2. Confirm log shipping is occurring between the sites
SQL*Plus: Release 11.2.0.3.0 Production on Thu Apr 18 12:08:18 2013
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 297
Next log sequence to archive 299
Current log sequence 299
Primary Site Alert Log
Details the switching occurring and the shipping of the logs
Thu Apr 18 11:57:15 2013
SMCO started with pid=24, OS id=3796
Thu Apr 18 12:09:04 2013
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
LGWR: Standby redo logfile selected for thread 1 sequence 298 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 298 (LGWR switch)
Current log# 3 seq# 298 mem# 0: +DATA/rs1_stb/onlinelog/group_3.278.801239719
Current log# 3 seq# 298 mem# 1: +FRA/rs1_stb/onlinelog/group_3.315.801239719
Thu Apr 18 12:09:07 2013
Archived Log entry 380 added for thread 1 sequence 297 ID 0x6cd69690 dest 1:
Thu Apr 18 12:09:19 2013
LGWR: Standby redo logfile selected for thread 1 sequence 299 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 299 (LGWR switch)
Current log# 1 seq# 299 mem# 0: +DATA/rs1_stb/onlinelog/group_1.276.801239713
Current log# 1 seq# 299 mem# 1: +FRA/rs1_stb/onlinelog/group_1.327.801239715
Thu Apr 18 12:09:22 2013
Archived Log entry 382 added for thread 1 sequence 298 ID 0x6cd69690 dest 1:
Standby Site Alert Log
Details the receiving of the logs in the Snapshot Standby
Thu Apr 18 11:52:11 2013
RFS[4]: Assigned to RFS process 3799
RFS[4]: Selected log 5 for thread 1 sequence 296 dbid 1823795963 branch 800115647
Archived Log entry 528 added for thread 1 sequence 296 ID 0x6cd69690 dest 3:
Thu Apr 18 11:53:30 2013
ALTER SYSTEM SET local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=IP)(PORT=1521))))' SCOPE=MEMORY SID='rs1';
Thu Apr 18 11:54:09 2013
Starting background process SMCO
Thu Apr 18 11:54:09 2013
SMCO started with pid=23, OS id=3812
Thu Apr 18 12:09:03 2013
RFS[2]: Selected log 5 for thread 1 sequence 298 dbid 1823795963 branch 800115647
Thu Apr 18 12:09:04 2013
Archived Log entry 529 added for thread 1 sequence 297 ID 0x6cd69690 dest 3:
Thu Apr 18 12:09:18 2013
RFS[2]: Selected log 4 for thread 1 sequence 299 dbid 1823795963 branch 800115647
Thu Apr 18 12:09:19 2013
Archived Log entry 530 added for thread 1 sequence 298 ID 0x6cd69690 dest 3:
Perform the conversion from a Snapshot Standby to a Physical Standby
Given the shipping is successful and the broker configuration is begin reported as healthy the conversion back to a physical standby can be performed.
1. Start the broker command line and ensure a sys@TNSALIAS connection is made to ensure a successful shutdown and startup of the standby site required throughout this process.
Password:
Connected.
2. Issue the convert command from the broker
The convert command will perform the following steps
- Shutdown snapshot standby down and restart it to mount
Operation requires shutdown of instance "rs1" on database "rs1"
Shutting down instance "rs1"...
Database closed.
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "rs1" on database "rs1"
Starting instance "rs1"...
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Database mounted.
- Another shutdown of the standby is initiated once the flashback operation has been performed. This flashback will set the standby site back to a time prior to the conversion to a snapshot standby.
Operation requires shutdown of instance "rs1" on database "rs1"
Shutting down instance "rs1"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
- The Standby site which has now been converted back to a Physical Standby site will now be restarted.
Starting instance "rs1"...
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Database mounted.
Database "rs1" converted successfully
Alert Log Extract from the Standby Site detailing the change from Snapshot Standby to Physical Standby
..
.
Fri Apr 19 11:41:46 2013
Shutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
..
.
Fri Apr 19 11:41:55 2013
NOTE: Deferred communication with ASM instance
NOTE: deferred map free for map id 12
Completed: alter database CLOSE NORMAL
alter database DISMOUNT
Shutting down archive processes
Archiving is disabled
..
.
Fri Apr 19 11:42:03 2013
Instance shutdown complete
Fri Apr 19 11:42:04 2013
Starting ORACLE instance (normal)
..
.
Fri Apr 19 11:42:33 2013
RSM0 started with pid=41, OS id=13962
alter database convert to physical standby
ALTER DATABASE CONVERT TO PHYSICAL STANDBY (rs1)
krsv_proc_kill: Killing 4 processes (all RFS)
Flashback Restore Start
..
.
Fri Apr 19 11:42:50 2013
Flashback Restore Complete
Drop guaranteed restore point
Guaranteed restore point dropped
Deleted Oracle managed file +FRA/rs1/flashback/log_6.412.802083919
Deleted Oracle managed file +FRA/rs1/flashback/log_4.265.800203569
Deleted Oracle managed file +FRA/rs1/flashback/log_3.308.801298337
Clearing standby activation ID 1836586315 (0x6d78154b)
The primary database controlfile was created using the
'MAXLOGFILES 16' clause.
There is space for up to 13 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Fri Apr 19 11:42:50 2013
ARC2: Becoming the active heartbeat ARCH
Clearing online redo logfile 1 +DATA/rs1/onlinelog/group_1.261.800115647
Clearing online log 1 of thread 1 sequence number 7
Clearing online redo logfile 1 complete
Clearing online redo logfile 2 +DATA/rs1/onlinelog/group_2.262.800115651
Clearing online log 2 of thread 1 sequence number 8
Clearing online redo logfile 2 complete
Clearing online redo logfile 3 +DATA/rs1/onlinelog/group_3.263.800115655
Clearing online log 3 of thread 1 sequence number 6
Clearing online redo logfile 3 complete
Completed: alter database convert to physical standby
Fri Apr 19 11:43:01 2013
Primary database is in MAXIMUM PERFORMANCE mode
Changing standby controlfile to MAXIMUM PERFORMANCE mode
RFS[4]: Assigned to RFS process 13967
RFS[4]: Selected log 4 for thread 1 sequence 304 dbid 1823795963 branch 800115647
Fri Apr 19 11:43:03 2013
Shutting down instance (immediate)
Shutting down instance: further logons disabled
..
.
Fri Apr 19 11:43:04 2013
NOTE: Deferred communication with ASM instance
All dispatchers and shared servers shutdown
alter database CLOSE NORMAL
ORA-1109 signalled during: alter database CLOSE NORMAL...
alter database DISMOUNT
Shutting down archive processes
Archiving is disabled
..
.
Completed: alter database DISMOUNT
..
.
Fri Apr 19 11:43:16 2013
Instance shutdown complete
Fri Apr 19 11:43:17 2013
Starting ORACLE instance (normal)
..
.
Fri Apr 19 11:43:31 2013
ARC3 started with pid=32, OS id=14084
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Physical Standby Database mounted.
Lost write protection disabled
ARC2: Becoming the active heartbeat ARCH
Completed: alter database mount
..
.
Fri Apr 19 11:43:44 2013
RSM0 started with pid=39, OS id=14112
ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='rs1';
ALTER SYSTEM SET log_archive_format='%t_%s_%r.dbf' SCOPE=SPFILE SID='rs1';
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE
Attempt to start background Managed Standby Recovery process (rs1)
Fri Apr 19 11:43:48 2013
MRP0 started with pid=40, OS id=14114
MRP0: Background Managed Standby Recovery process started (rs1)
started logmerger process
Fri Apr 19 11:43:54 2013
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /tmp/1_284_800115647.dbf
Media Recovery Log /u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_285_800115647.dbf
Fri Apr 19 11:43:56 2013
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE
Media Recovery Log /u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_286_800115647.dbf
Media Recovery Log /tmp/1_287_800115647.dbf
..
.
Media Recovery Log /u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_302_800115647.dbf
Media Recovery Log +FRA/rs1/archivelog/2013_04_19/thread_1_seq_303.308.813152615
Media Recovery Log +FRA/rs1/archivelog/2013_04_19/thread_1_seq_304.265.813152621
Media Recovery Waiting for thread 1 sequence 305 (in transit)
Recovery of Online Redo Log: Thread 1 Group 5 Seq 305 Reading mem 0
Mem# 0: +DATA/rs1/onlinelog/group_5.269.800367453
Mem# 1: +FRA/rs1/onlinelog/group_5.316.800367455
Standby Data Guard Broker Log detailing the change from Snapshot Standby to Physical Standby
04/18/2013 13:53:50
Creating process RSM0
04/18/2013 13:53:54
Process RSM0 re-created with PID = 7625
04/18/2013 13:56:39
Process RSM0, PID = 7625, will be killed
04/18/2013 13:56:46
Creating process RSM0
04/18/2013 13:56:50
Process RSM0 re-created with PID = 7635
04/19/2013 11:41:37
Data Guard notifying Oracle Clusterware of database role change
conversion to physical standby requires this database be restarted to the mounted state
04/19/2013 11:41:52
Notifying DMON of db close
Notifying RSM0 of db close
04/19/2013 11:41:56
Data Guard Broker shutting down
posting shutdown message to primary database 0x02001000
RSM0 successfully terminated
04/19/2013 11:41:58
Command CONVERT DATABASE rs1 completed with warning ORA-16570
>> DMON Process Shutdown <<
04/19/2013 11:42:22
>> Starting Data Guard Broker bootstrap <<
Broker Configuration File Locations:
dg_broker_config_file1 = "+DATA/rs1/dr1rs1.dat"
dg_broker_config_file2 = "+FRA/rs1/dr2rs1.dat"
04/19/2013 11:42:27
DMON Registering service rs1_DGB with listener(s)
Broker Configuration: "rs1_dg"
Protection Mode: Maximum Performance
Fast-Start Failover (FSFO): Disabled, flags=0x0, version=3
Primary Database: rs1_stb (0x02010000)
Standby Database: rs1, Enabled Snapshot Standby (0x01010000)
04/19/2013 11:42:28
Data Guard notifying Oracle Clusterware of database role change
04/19/2013 11:42:32
Creating process RSM0
04/19/2013 11:43:00
CONVERT to PHYSICAL succeeded. Restart required.
04/19/2013 11:43:09
Data Guard Broker shutting down
posting shutdown message to primary database 0x02001000
RSM0 successfully terminated
04/19/2013 11:43:12
>> DMON Process Shutdown <<
04/19/2013 11:43:35
>> Starting Data Guard Broker bootstrap <<
Broker Configuration File Locations:
dg_broker_config_file1 = "+DATA/rs1/dr1rs1.dat"
dg_broker_config_file2 = "+FRA/rs1/dr2rs1.dat"
04/19/2013 11:43:39
DMON Registering service rs1_DGB with listener(s)
Broker Configuration: "rs1_dg"
Protection Mode: Maximum Performance
Fast-Start Failover (FSFO): Disabled, flags=0x0, version=3
Primary Database: rs1_stb (0x02010000)
Standby Database: rs1, Enabled Physical Standby (0x01010000)
Physical standby bootstrap requires Oracle Clusterware buildup
04/19/2013 11:43:44
rs1 version check successfully completed
rs1 has current configuration metadata,
completing bootstrap
Creating process RSM0
04/19/2013 11:43:54
Notifying Oracle Clusterware that database is open
Data Guard notifying Oracle Clusterware to start services and other instances change
REFERENCES
NOTE:443720.1 - Using Snapshot Standby Database.NOTE:1623815.1 - Data Guard Snapshot Standby Archive Redo Log Management and Configuration
Thursday, July 8, 2021
Primary Note For Oracle Recovery Manager (RMAN) (Doc ID 1116484.1)
In this Document
| Details |
| Actions |
| Introduction |
| Getting started with RMAN |
| Backing up Database files using RMAN and Maintaining the backup records. |
| Restore and recovery techniques/scenarios using RMAN. |
| Tablespace point in time recovery |
| Rman Transportable tablespaces and database. |
| Rman Performance. |
| RMAN and Media managers |
| Rman and Dataguard |
| Rman and Rac |
| Rman and Corruption |
| Related Primary Notes |
| Using My Oracle Support Effectively |
| Generic Links |
| References |
APPLIES TO:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
DETAILS
This Primary 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 Primary 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 Primary Notes
- Using My Oracle Support Effectively
- Generic Links
ACTIONS
Introduction
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
Oracle Server - Enterprise Edition - Version: 12.1.0.1 to 12.2.0.x
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,12.1,12.2 and FAQ on RMAN.
Note.469777.1 RMAN - Frequently Asked Question (FAQ)
Note 809867.1 RMAN 11gR1: New Features
Note 1115423.1 RMAN Enhancements In Oracle 11g.
Note 1534487.1 RMAN Enhancements in Oracle 12c
Note 1521005.1 RMAN Pluggable Database Backup and Recovery in a Multitenant Environment
Note 1521075.1 RMAN Pluggable Database Point in Time Recovery
Rman compatibility
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, troubleshooting flash recovery area issues.
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?
Document 2308215.1 12.2 Perform Flashback at PDB Level
Document 1521524.1 RMAN RECOVER TABLE Feature New to Oracle Database 12c
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 behavior and troubleshooting them.
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.467969.1 How To Configure RMAN Recovery Catalog Using Enterprise Manager DB Console.
Note 2039848.1 Known Issues with RMAN Oracle12c Catalog
Backing up Database files using RMAN and Maintaining the 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
- Rman backup concepts - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#i1006083
- Backing up database - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#i1005689
- Advanced backups - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckad.htm#CEGHFJCF
- Backup maintenance - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmmaint.htm#j1006083
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 Manager
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 the Repository and Spfile/Init.ora Files Are Also Lost
Note.223543.1 How to Recover From a DROP / TRUNCATE / DELETE TABLE with RMAN
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 HowTo 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.358171.1 Oracle10g RMAN will not restore in parallel from tape
Document 2300465.1 12.2 NEW FEATURE : -RECOVER DATABASE UNTIL AVAILABLE REDO
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 1531202.1 RMAN TSPITR Tips and Tricks
Note 304305.1 Limitations of RMAN TSPITR
Rman Transportable tablespaces 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.455593.1 Creating a transportable tablespace set from RMAN backupsets
Note.831223.1 Using Rman Incremental backups To Update Transportable Tablespaces.
Note.1401921.1 Cross-Platform Database Migration (across same endian) using RMAN Transportable Database
Note.733205.1 Migration of Oracle Database Instances Across OS Platforms
Note 1389592.1 11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
Note 2005729.1 12C - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
Document 2307383.1 12.2 RMAN Cross Platform Tablespace Transport Over Network
Document 2307358.1 12.2 RMAN Cross Platform Transport Of TDE-encrypted tablespace
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.452868.1 RMAN 'Duplicate Database' Feature in 11G
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.1910175.1 RMAN DUPLICATE / RESTORE including Standby in ASM with OMF / non-OMF / Mixed Name for Datafile / Online Log / Controlfile
Note.1913937.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
Note.1079563.1 RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support
Note 1375864.1 Perform Backup Based RMAN DUPLICATE Without Connecting To Target Database For Both Disk & Tape Backups
Document 2022820.1 Upgrade to 12c(12.1 /12.2) through RMAN Duplicate using BACKUP LOCATION with NOOPEN clause
Rman Performance.
Note 740911.1 RMAN Restore Performance
Note 247611.1 Known RMAN Performance Problems
Note 579158.1 Advise On How To Improve Rman Performance
Note 463227.1 Oracle10g RMAN Recovery Catalog Known Performance Issues
Note 1487262.1 Script to monitor RMAN Backup and Restore Operations
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 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.357759.1 Known RMAN - Dataguard Problems
Note 836986.1 Steps to perform for Rolling forward a standby database using RMAN Incremental Backup.
Rman and Rac
Note.415579.1 HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node
Note.1913937.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.561010.1 Which Blocks Will RMAN Check For Corruption Or Include In A Backupset?
Note 428570.1 Best Practices for Avoiding and Detecting Corruption
Note.472231.1 How to identify all the Corrupted Objects in the Database reported by RMAN
Note 471716.1 11g New Feature V$Database_block_corruption Enhancements and Rman Validate Command
Related Primary Notes
Note 1096952.1 Primary Note for Real Application Clusters (RAC) Oracle Clusterware and Oracle Grid Infrastructure
Note 1088018.1 Primary Note for Oracle Database Corruption
Note 1101938.1 Primary Note for Data Guard
Using My Oracle Support Effectively
Note 166650.1 Working Effectively With Global Customer Support
Note 199389.1 How To Request Management Attention to a Service Request (SR) with Oracle Support Services
Generic Links
Note 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution
Note 756671.1 Oracle Recommended Patches -- Oracle Database
Note 268895.1 Oracle Database Patchset Information, Versions 10.2.0 to 12.1.0
Note 161549.1 Oracle Database Server and Networking Patches for Microsoft Platforms
Note 161818.1 Oracle Database (RDBMS) Releases Support Status Summary
REFERENCES
NOTE:360962.1 - Manual Completion of a Failed RMAN Backup based DuplicateNOTE:419137.1 - How To Restore Rman Backups On A Different Node When The Directory Structures Are Different
NOTE:428570.1 - Best Practices for Avoiding and Detecting Corruption
NOTE:452529.1 - Recovery catalog for RMAN backup
NOTE:452868.1 - RMAN 'Duplicate From Active Database'
NOTE:455593.1 - Creating a transportable tablespace set from RMAN backupsets
NOTE:472536.1 - 10g RMAN Benefits of Simplified Recovery Through Resetlogs.
NOTE:550082.1 - HOW TO CATALOG TAPE BACKUP PIECES
NOTE:560133.1 - Benefits Of Using Flash Recovery Area
NOTE:561010.1 - Which Blocks Will RMAN Check For Corruption Or Include In A Backupset?
NOTE:382669.1 - DUPLICATE (Backup based) DATABASE from non ASM to ASM (vice versa) to different host
NOTE:388422.1 - Top 10 Backup and Recovery Best Practices
NOTE:351455.1 - Oracle Suggested Strategy & Backup Retention
NOTE:1910175.1 - RMAN DUPLICATE / RESTORE including Standby in ASM with OMF / non-OMF / Mixed Name for Datafile / Online Log / Controlfile
NOTE:848716.1 - Using RMAN Effectively In A Dataguard Environment.
NOTE:854428.1 - Patch Set Updates for Oracle Products
NOTE:809867.1 - RMAN 11gR1 : New Features
NOTE:829755.1 - Space issue in Fast / Flash Recovery Area - FRA Full
NOTE:268895.1 - Oracle Database Patchset Information, Versions 10.2.0 to 12.2.0
NOTE:1531202.1 - RMAN TSPITR Tips and Tricks
NOTE:199389.1 - How To Request Management Attention on a Service Request (SR) with Oracle Support Services
NOTE:304305.1 - Limitations of RMAN TSPITR
NOTE:735953.1 - This document has been replaced with more recent information on this topic. Please refer to more recent documentation.
NOTE:740911.1 - RMAN Restore Performance
NOTE:745798.1 - RMAN: Merged Incremental Backup Strategies
NOTE:360416.1 - Getting Started with Recovery Manager (RMAN)
NOTE:223543.1 - How to Recover From a DROP / TRUNCATE / DELETE TABLE with RMAN
NOTE:1199803.1 - Primary Note For Oracle Backup And Recovery
NOTE:888.1 - Primary Note for Database Proactive Patch Program
NOTE:1101938.1 - Primary Note for Data Guard
NOTE:1389592.1 - 11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
NOTE:2005729.1 - 12C - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
NOTE:1375864.1 - Perform Backup Based RMAN DUPLICATE Without Connecting To Target Database For Both Disk & Tape Backups
NOTE:227517.1 - Main Index of Common Causes for ORA-19511
NOTE:360443.1 - RMAN Backup Performance
NOTE:369644.1 - Frequently Asked Questions about Restoring Or Duplicating Between Different Versions And Platforms
NOTE:357759.1 - Known RMAN - Dataguard Problems
NOTE:358171.1 - Oracle10g: RMAN will not restore in parallel from tape
NOTE:472231.1 - How to identify all the Corrupted Objects in the Database with RMAN
NOTE:243760.1 - RMAN: RAC Backup, Restore and Recovery using RMAN
NOTE:1088018.1 - Primary Note for Handling Oracle Database Corruption Issues
NOTE:1115423.1 - Rman Enhancements In Oracle 11g.
NOTE:305812.1 - Flash Recovery area - Space management Warning & Alerts
NOTE:463875.1 - Frequently asked questions on Rman backup retention policy
NOTE:833663.1 - Flash Recovery Area - FAQ
NOTE:262853.1 - RMAN Fast Incremental Backups using BCT = Block Change Tracking file
NOTE:312737.1 - RMAN and Specific Media Managers Environment Variables.
NOTE:315098.1 - How is the space pressure managed in the Flash Recovery Area - An Example.
NOTE:463227.1 - Oracle10g RMAN Recovery Catalog Known Performance Issues
NOTE:305651.1 - How to change Flash Recovery Area to a new location ?
NOTE:371556.1 - How to Migrate to different Endian Platform Using Transportable Tablespaces With RMAN
NOTE:372996.1 - Using RMAN to Restore and Recover a Database When the Repository and Spfile/Init.ora Files Are Also Lost
NOTE:293717.1 - How to duplicate a database to a previous Incarnation
NOTE:1079563.1 - RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support
NOTE:247611.1 - Known RMAN Performance Problems
NOTE:305796.1 - RMAN and Flash Recovery Area
NOTE:305810.1 - Configuring file creation in Flash recovery area and order of Precedence
NOTE:467969.1 - How To Configure RMAN Recovery Catalog Using Enterprise Manager DB Console.
NOTE:469777.1 - RMAN -- Frequently Asked Question (FAQ)
NOTE:1913937.1 - STEP BY STEP RMAN DUPLICATE Database From RAC ASM To RAC ASM
NOTE:403883.1 - How To Restore Controlfile From A Backupset Without A Catalog Or Autobackup
NOTE:415579.1 - How To Restore RMAN Disk backups of RAC Database to Single Instance On Another Node
NOTE:137181.1 - RMAN Backup Shell Script Example
NOTE:1401921.1 - Cross-Platform Database Migration (across same endian) using RMAN Transportable Database
NOTE:144911.1 - RMAN : Block-Level Media Recovery - Concept & Example
NOTE:836658.1 - Identify the Corruption Extension for Block Corruption, Table/Index Inconsistency, Data Dictionary and Lost Writes
NOTE:840647.1 - How to use Rman Duplicate on ASM/RAC/OMF/Single Instance
NOTE:335851.1 - Automatic TSPITR in 10G RMAN -A walk Through
NOTE:580414.1 - RMAN - How to restore the controlfile using RMAN
NOTE:161818.1 - Oracle Database (RDBMS) Releases Support Status Summary
NOTE:2039848.1 - Known Issues with RMAN Oracle12c Catalog
NOTE:166650.1 - Working Effectively With Oracle Support - Best Practices
NOTE:747242.5 - My Oracle Support FAQ
NOTE:733205.1 - Migration Of An Oracle Database Across OS Platforms (Generic Platform)
NOTE:388424.1 - How To Create A Production (Full or Partial) Duplicate On The Same Host
NOTE:388431.1 - Creating a Duplicate Database on a New Host (non ASM).
NOTE:1487262.1 - Script to monitor RMAN Backup and Restore Operations
NOTE:305648.1 - What is a Flash / Fast Recovery Area and how to configure it ?
NOTE:1061295.1 - Patch Set Updates - One-off Patch Conflict Resolution
NOTE:94114.1 - Backup and Recovery Scenarios
NOTE:462978.1 - Rman backup retention policy
NOTE:942418.1 - How To Verify A Media Manager Layer Installation ?
NOTE:228257.1 - RMAN 'Duplicate Database' Feature in Oracle9i / 10G and 11G
NOTE:579158.1 - Advise On How To Improve Rman Performance
NOTE:73431.1 - RMAN Compatibility Matrix
-
In this Document Goal Ask Questions, Get Help, And Share Your Experiences With This Article Solution 12c TDE FAQ documentation Quick...
-
This document describes how to develop and deploy customizations in an Oracle E-Business Suite Release 12.2 environment. Follow thes...
-
This document also provides links to two presentations on the subject: Oracle OpenWorld presentation "Technical Upgrade Best Practice...
