RMAN备份之丢失数据文件及控制文件的恢复
2015-03-31 10:01
711 查看
About Recovery with a Backup Control File
If all copies of the current control file are lost or damaged, then you must restore and mount a backup control file. You must then run the RECOVER command, even if no data files have been restored, and open the database with the RESETLOGS option. If some copies of the current control file are usable, however, then you can follow the procedure in "Responding to the Loss of a Subset of the Current Control Files" and avoid the recovery and RESETLOGS operation. When RMAN is connected to a recovery catalog, the recovery procedure with a backup control file is identical to recovery with a current control file. The RMAN metadata missing from the backup control file is available from the recovery catalog. The only exception is if the database name is not unique in the catalog, in which case you must use SET DBID command before restoring the control file.
1. Start RMAN and connect to a target database.
2. Start the target instance without mounting the database. RMAN>STARTUP NOMOUNT; --控制文件丢失或损坏,只能将启动到nomount
3. Restore the control file
RMAN> SET DBID 320066378; # (Optional) If the database name is not unique, you need to specify the DBID
RMAN> RUN
{
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'autobackup_format';
RESTORE CONTROLFILE FROM AUTOBACKUP; --从自动备份中恢复控制文件
}
4. Start the target instance with mounting the database. RMAN>STARTUP MOUNT; --控制文件已恢复,可mount数据文件
5. Restore the data files; RMAN>RESTORE DATABASE; --restore/recover损坏的数据文件
6. Recover the database; RMAN>RECOVER DATABASE;
7. Open the database with RESETLOGS option; RMAN> ALTER DATABASE OPEN RESETLOGS; --以resetlog方式打开数据库
If all copies of the current control file are lost or damaged, then you must restore and mount a backup control file. You must then run the RECOVER command, even if no data files have been restored, and open the database with the RESETLOGS option. If some copies of the current control file are usable, however, then you can follow the procedure in "Responding to the Loss of a Subset of the Current Control Files" and avoid the recovery and RESETLOGS operation. When RMAN is connected to a recovery catalog, the recovery procedure with a backup control file is identical to recovery with a current control file. The RMAN metadata missing from the backup control file is available from the recovery catalog. The only exception is if the database name is not unique in the catalog, in which case you must use SET DBID command before restoring the control file.
1. Start RMAN and connect to a target database.
2. Start the target instance without mounting the database. RMAN>STARTUP NOMOUNT; --控制文件丢失或损坏,只能将启动到nomount
3. Restore the control file
RMAN> SET DBID 320066378; # (Optional) If the database name is not unique, you need to specify the DBID
RMAN> RUN
{
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'autobackup_format';
RESTORE CONTROLFILE FROM AUTOBACKUP; --从自动备份中恢复控制文件
}
4. Start the target instance with mounting the database. RMAN>STARTUP MOUNT; --控制文件已恢复,可mount数据文件
5. Restore the data files; RMAN>RESTORE DATABASE; --restore/recover损坏的数据文件
6. Recover the database; RMAN>RECOVER DATABASE;
7. Open the database with RESETLOGS option; RMAN> ALTER DATABASE OPEN RESETLOGS; --以resetlog方式打开数据库
相关文章推荐
- [强烈推荐]Oracle:只有rman备份(数据,参数,日志,控制文件全丢失)的恢复
- 丢失oracle参数文件,数据文件以及控制文件,只有rman备份的恢复
- Oracle:只有rman备份(数据,参数,日志,控制文件全丢失)的恢复
- Oracle:只有rman备份(数据,参数,日志,控制文件全丢失)的恢复
- oracle数据库中的内容全部丢失,只有RMAN的备份文件(包括数据,参数,控制文件),恢复数据库到备份状态
- Oracle:只有rman备份(数据,参数,日志,控制文件全丢失)的恢复
- RMAN 备份恢复 删除表空间后控制文件丢失
- rman备份丢失控制文件恢复
- RMAN备份与恢复之可脱机数据文件丢失
- rman 控制文件 参数文件数据文件丢失恢复
- ORACLE基础学习-RMAN应用之(归档模式无备份,丢失数据文件的恢复)
- 使用RMAN的备份及恢复一例-丢失所有控制文件
- RMAN备份恢复 控制文件和归档日志丢失情况
- RMAN备份与恢复之控制文件丢失
- RMAN数据库恢复 之归档模式有(无)备份-丢失数据文件的恢复
- rman实验之归档模式有备份,正常关机丢失数据文件的恢复
- Oracle rman不完全恢复(数据文件,归档日志,控制文件全部丢失)
- Oracle - 使用RMAN的备份及恢复一例-丢失所有控制文件
- ORACLE11g 没有控制文件如何通过rman备份恢复数据的详细实战过程
- 拥有RMAN全备(缺少后增文件),丢失全部数据文件,控制文件的恢复