<P></P><P>运用平台: Oracle Server - Enterprise Edition - Version: 9.2.0.5 to 10.1.0.4 - Release: 9.2 to 10.1 Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 10.2.0.5 [Release: 9.2 to 10.2] 本文档中的信息也适用于其他平台 错误: RMAN duplicate数据库报错: RMAN-06053: unable to perform media recovery because of missing log 由于缺少日志文件,不能执行介质恢复 RMAN-06025: no backup of log thread 1 seq 182 scn 43214333 found to restore Screen shot posted to the tar verifies issue showing error: RMAN-06053: unable to perform media recovery because of missing log RMAN-06025: no backup of log thread 1 seq 182 scn 43214333 found to restore 原因: 当目标数据库运行在归档模式下,RMAN 将会尝室做恢复尽管When the target database is running in ARCHIVELOG mode, RMAN will want to do some recovery even when the backup restored is a cold (offline) backup. 产生以上的错误的缘由基于RMAN 的功能 解决方案: 请按以下步骤执行解决方案: 1. 一旦RMAN失败 2. 登录到辅助实例 3. select open_mode from v$database;查看数据库的状态 4. 如果没有被挂载,挂载辅助实例 5. select file#, status, checkpoint_change#, fuzzy from v$datafile_header; ——检查checkpoint_change#是相同的 ——检查fuzzy=NO 6. .假设在检查#5时所有的都符合要求 7. recover database using backup controlfile until cancel; ——type cancel; 当恢复cancelled时,如果收到ORA-1547错误,是因为你的文件不一致 8. alter database open resetlogs; 9. shutdown immediate 10. startup mount 11. 在操作系统上dbnewid来改变dbid; nid TARGET=SYS/oracle 12. shutdown immediate 13. startup mount; 14. alter database open resetlogs; 15. Select dbid from v$database; /确认此时的dbid不同于TARGET / 出现的错误: ORA-1547; RMAN-6025; RMAN-6053</P><P></P>
|