Database Reference
In-Depth Information
channel ORA_DISK_1: control file restore from AUTOBACKUP complete
output file name=C:\ORACLE\ORADATA\RCAT\CONTROL01.CTL
output file name=C:\ORACLE\ORADATA\RCAT\CONTROL02.CTL
output file name=C:\ORACLE\ORADATA\RCAT\CONTROL03.CTL
Finished restore at 28-SEP-13
RMAN> Alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> Recover database;
Starting recover at 28-SEP-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=153 device type=DISK
starting media recovery
archived log for thread 1 with sequence 1 is already on disk as file
C:\ORACLE\ORADATA\RCAT\REDO01.LOG
archived log for thread 1 with sequence 2 is already on disk as file
C:\ORACLE\ORADATA\RCAT\REDO02.LOG
archived log file name=C:\ORACLE\ORADATA\RCAT\REDO01.LOG thread=1 sequence=1
archived log file name=C:\ORACLE\ORADATA\RCAT\REDO02.LOG thread=1 sequence=2
media recovery complete, elapsed time: 00:00:02
Finished recover at 28-SEP-13
RMAN> alter database open resetlogs;
Statement processed
You can also use the
RESTORE CONTROLFILE
command to restore a control file to a differ-
ent location and filename using the
TO
keyword, as shown in this example:
Restore controlfile to '/tmp/orcl.ctl' from autobackup;
Recovering Control Files When Not Using Control-File Autobackups
If you have not enabled control-file autobackups, you need to use the recovery catalog
to restore a control file (there are other ways—see the sidebar “Emergency Control-File
Recoveries”). Simply follow these steps:
1.
Start RMAN and connect to the recovery catalog.
2.
Use the
STARTUP FORCE NOMOUNT
command to start the database instance.
3.
Issue the
RESTORE CONTROLFILE
command and RMAN will restore the control file.
4.
Mount the database with the
ALTER DATABASE MOUNT
command.
5.
Issue a
RECOVER DATABASE
command.
6.
Open the database with the
ALTER DATABASE OPEN RESETLOGS
command.
Search WWH ::
Custom Search