-
Recovery of a dropped tablespace
-
NOARCHIVELOG Database Recovery
-
RMAN Restore on another machine with different file system- same database name
-
RMAN duplicate database on the same host
-
Loss Of All Files – Disaster Recovery
-
Incomplete Recovery (until point in time)
-
Incomplete Recovery (until log sequence)
-
Loss of all online redo log files
-
Loss of all controlfiles
-
Recovery when no backup exists of a datafile
-
Corrupted Block Recovery
-
Loss of Non SYSTEM datafile
-
Tablespace Recovery
-
Tesing the full restore and recovery of a database backup on another test or scratch server
-
Refreshing a Test or Development Database from a Production Database RMAN backup
-
Recovery through RESETLOGS and reset of incarnation
-
Performing a database clone using a Data Guard physical standby database
-
Diagnosing and Repairing Failures using the 11g Data Recovery Advisor (loss of control files)
-
Restoring an ASM backup to non-ASM and Restoring from RAC to single-instance
-
Recovery from loss of SPFILE (with and without AUTOBACKUP configured)
The following two tabs change content below.
V.V good help
Thanks
Gurwinder singh
Cell no -> 09871042700
Gavin,
Good exercises…but few things to update.
1. Without having allocate channels, host cpu & disk I/O will consumes alot. As I tried to had “top” & “glance” in parallel, and i could notice it’s consuming alot when trying to restore < 100 GB of database on HP-UX ia64 which has 16 GB of ram. Well, we could release those soon after completion
2. Also in case of back-dated restoration where by you need to restore the control files from backup piece tags; at that stage , database will not be in a mounted state. In such cases, when you login to rman, we might have to get dbid from "rc_database" and have to set dbid prior to restoration.
Thanks for sharing good workshop exercises…and request if you could thru light on advance RMAN concepts.
Rgrds
ATA
Hello,
Thanks a lot for all this examples and documentation, could you please check the link of ” Restoring an ASM backup to non-ASM and Restoring from RAC to single-instance” in recovery scenarios , isn’t found
best regards
Lahcen
Hi – thanks for pointing that out – its fixed now – regards Gavin