Database Reference
In-Depth Information
All that remains is the restore of the spfile:
RMAN> Restore SPFILE from autobackup;
Starting restore at 28-SEP-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=98 device type=DISK
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20130928
channel ORA_DISK_1: AUTOBACKUP found:
c:\oracle\controlfilebackup\c-437680418-20130928-00
channel ORA_DISK_1: restoring SPFILE from AUTOBACKUP
c:\oracle\controlfilebackup\c-437680418-20130928-00
channel ORA_DISK_1: SPFILE restore from AUTOBACKUP complete
Finished restore at 28-SEP-13
You can also include the SET commands within the confines of a RUN block, as shown here:
RUN
{
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO
'c:\oracle\controlfilebackup\%F';
RESTORE CONTROLFILE FROM AUTOBACKUP MAXSEQ 100;
}
You can now open the database with the STARTUP FORCE command, as shown here:
RMAN> startup force
Oracle instance started
database mounted
database opened
Total System Global Area 535662592 bytes
Fixed Size 1334380 bytes
Variable Size 369099668 bytes
Database Buffers 159383552 bytes
Redo Buffers 5844992 bytes
To summarize the steps for this recovery, here they are:
1. Start up the database in NOMOUNT mode.
2. Set the database DBID.
3. Use the SET command to set the RMAN parameter CONTROLFILE AUTOBACKUP FORMAT
to point to the correct control-file autobackup location.
4. Restore the SPFILE with the RESTORE SPFILE FROM AUTOBACKUP command.
5. Recycle the database to reread the newly recovered spfile parameter file.
Search WWH ::




Custom Search