Database Reference
In-Depth Information
C:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
channel ORA_DISK_1: restoring datafile 00004 to
C:\ORACLE\FAST_RECOVERY_AREA\ORCL
\DATAFILE\O1_MF_USERS_4G2Q1YTC_.DBF
channel ORA_DISK_1: reading from backup piece
C:\ORACLE\FAST_RECOVERY_AREA\ORCL
\BACKUPSET\2013_09_29\O1_MF_NNNDF_SILVER_COPY_4G2DQT1Y_.BKP
RMAN> recover database until time '09/29/2013:15:00:00';
Starting recover at 10/02/2013 00:09:47
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 5 is already on disk as file
C:\ORACLE\PRODUCT\12.1.0\DB_1\RDBMS\ARC00005_0666708076.001
archived log for thread 1 with sequence 6 is already on disk as file
C:\ORACLE\FAST_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_09_30
\O1_MF_1_6_4G4QPYYR_.ARC
archived log file name=
C:\ORACLE\PRODUCT\12.1.0\DB_1\RDBMS\ARC00005_0666708076.001
thread=1 sequence=5
media recovery complete, elapsed time: 00:00:14
Finished recover at 10/02/2013 00:10:03
RMAN> alter database open resetlogs;
database opened
You could also have executed this restore using the following commands:
shutdown abort
startup mount
run {
set until time '09/30/2013:18:00:00';
restore database;
recover database;
}
sql 'alter database open resetlogs';
One time when you might need to perform point-in-time recovery is during a database
recovery after a complete loss of the online redo logs of the database. This might include cases
when just the online redo logs were lost or cases when the entire database was lost, including
the online redo logs. While it is possible to save your database data in the event of such a loss
(see Chapter 2 for more information on such a case), it is likely that you will have to perform
a point-in-time recovery to get your database operational again. This will, of course, result in
some data loss.
You can also restore databases using tags. A tag allows you to choose a specific backup
image that you want to use for the restore. You can also use a tag during a recovery to indicate
Search WWH ::
Custom Search