Backing Up Oracle - Computing at Cornell

Information from that command was used in the set until portion of the
RMAN restore script:
RMAN> run {
2> set until logseq = 69 thread = 1;
3> allocate channel t1 type 'sbt_tape';
4> restore controlfile;
5> alter database mount;
6> restore database;
7> recover database delete archivelog;
8> alter database open resetlogs;
9> release channel t1;
10> }
In this example:
- set until logseq = 69 thread = 1; specifies a logseq of 69 and a thread of 1
for the subsequent restore and recovery commands. This information
was collected from the list backup of archivelog all; command.
- restore controlfile causes RMAN to restore the controlfiles to all
control file destinations. The control files are not restored by the
restore database command.
- restore database restores all datafiles belonging to the database.
Existing datafiles are overwritten.
- recover database delete archivelog deletes restored archived logs that
are no longer needed.
- alter database open resetlogs is the only way to open the database
again, because the data in the redo logs cannot be used any longer.
After a successful database point-in-time recovery, a consistent backup of
the database is required.
12.3.4 Duplicate database
For an example of duplicating a database, see Section 8.3.4, “Duplicate
database” on page 114.
Chapter 12. Recovering Oracle databases on Windows 2000 195