265.632440415
archived log for thread 1 with sequence 143
is already on disk as file
+RECOV/dw/archivelog/2007_09_04/
thread_1_seq_143.349.632442295
archived log for thread 1 with sequence 144
is already on disk as file
+RECOV/dw/archivelog/2007_09_04/
thread_1_seq_144.350.632442297
archived log for thread 1 with sequence 145
is already on disk as file
+RECOV/dw/archivelog/2007_09_04/
thread_1_seq_145.351.632442303
archived log file
name=+RECOV/dw/archivelog/2007_09_04/
thread_1_seq_142.265.632440415 thread=1 sequence=142
archived log file
name=+RECOV/dw/archivelog/2007_09_04/
thread_1_seq_143.349.632442295 thread=1 sequence=143
media recovery complete, elapsed time: 00:00:35
Finished recover at 04-SEP-07
starting full resync of recovery catalog
full resync complete
RMAN> alter database open;
database opened
RMAN>
The database is now open and available for use. RMAN will pick the most efficient way to
perform the requested operation, minimizing the number of files accessed or the number of disk I/
Os to bring the database back to a consistent state in as short a time as possible. In the previous
example, RMAN used a full database backupset and archived redo log files to recover the database.
During a recovery operation, RMAN may need to restore archived redo logs from tape; to
limit the amount of disk space used during a recovery operation, the recover command used in
the previous example could use the following options instead:
RMAN> recover database delete archivelog maxsize 2gb;
The parameter delete archivelog directs RMAN to remove archived log files from disk that
were restored from tape for this recovery option; the maxsize 2gb parameter restricts the amount
of space that can be occupied by restored archived log files at any point in time to 2GB.
Pages:
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708