dg备库恢复

最新推荐文章于 2025-02-11 17:02:44 发布

iteye_7084

最新推荐文章于 2025-02-11 17:02:44 发布

阅读量430

点赞数

CC 4.0 BY-SA版权

分类专栏： oracle数据库管理文章标签：数据库

本文链接：https://blog.youkuaiyun.com/iteye_7084/article/details/82525844

oracle数据库管理专栏收录该内容

59 篇文章

订阅专栏

本文介绍了在Oracle数据库中遇到的备库恢复问题及其解决方案。主要问题是由于dbf文件与控制文件版本不匹配导致的恢复失败。通过调整主库备份脚本顺序，先备份数据库加归档日志，再备份当前控制文件，最终成功解决了备库恢复的问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

在主库上执行：
执行全备：
RMAN> run{
allocate channel a1 type disk;
backup full database include current controlfile for standby plus archivelog ;
release channel a1;
}
rman target sys/oracle@orcl auxiliary /
duplicate target database for standby nofilenamecheck dorecover;
在备库上恢复时提示：
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/s01/oracle/app/oracle/oradata/orcl/system01.dbf'

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/16/2013 04:35:46
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 23 and starting SCN of 1135707 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 22 and starting SCN of 1135400 found to restore

错误大致意思：dbf文件与控制文件的版本号对不上

修改主库备份脚本：
1.backup database plus archivelog；
2.backup current controlfile for standdy；
再恢复，ok！

备库取消redo：alter database recover managed standby database cancel;

启用：alter database recover managed standby database using current logfile disconnect from session;

rman恢复：
duplicate target database for standby nofilenamecheck dorecover;