设为首页 加入收藏

TOP

oracle11g dataguard中standby库文件坏块的修复过程(七)
2015-11-21 01:29:04 来源: 作者: 【 】 浏览:2
Tags:oracle11g dataguard standby 文件 修复 过程
og list; Database log mode Archive Mode Automatic archival Enabled Archive destination /data/oracle/oradgdata/standby_archive Oldest online log sequence 38271 Next log sequence to archive 0 Current log sequence 38273 SQL> SQL> select * from z_z_test; ID ---------- 1 SQL>

看到log sequence已经增长到38273,日志应该应用过来了,然后去查询数据临时表z_z_test数据也已经过来了,证明修复OK,成功了。

5,后台alert日志有错误信息

Errors in file /oracle/app/oracle/diag/rdbms/pddgunq/powerdes/trace/powerdes_dbw0_14852.trc: ORA-01157: cannot identify/lock data file 201 - see DBWR trace file ORA-01110: data file 201: '/home/oradata/powerdes/temp01.dbf' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /oracle/app/oracle/diag/rdbms/pddgunq/powerdes/trace/powerdes_dbw0_14852.trc: ORA-01186: file 201 failed verification tests ORA-01157: cannot identify/lock data file 201 - see DBWR trace file ORA-01110: data file 201: '/home/oradata/powerdes/temp01.dbf' File 201 not verified due to error ORA-01157 Dictionary check complete Re-creating tempfile /home/oradata/powerdes/temp01.dbf Database Characterset is ZHS16GBK No Resource Manager plan active ********************************************************** WARNING: Files may exists in db_recovery_file_dest that are not known to the database. Use the RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If files cannot be cataloged, then manually delete them using OS command. One of the following events caused this: 1. A backup controlfile was restored. 2. A standby controlfile was restored. 3. The controlfile was re-created. 4. db_recovery_file_dest had previously been enabled and then disabled. ********************************************************** replication_dependency_tracking turned off (no async multimaster replication found) Physical standby database opened for read only access. Completed: alter database open Mon Oct 19 17:53:06 2015 alter database recover managed standby database disconnect from session Attempt to start background Managed Standby Recovery process (powerdes) Mon Oct 19 17:53:06 2015 MRP0 started with pid=48, OS id=15063 MRP0: Background Managed Standby Recovery process started (powerdes) started logmerger process Mon Oct 19 17:53:11 2015 Managed Standby Recovery not using Real Time Apply Parallel Media Recovery started with 16 slaves Waiting for all non-current ORLs to be archived... All non-current ORLs have been archived. Media Recovery Log /data/oracle/oradgdata/standby_archive/1_38271_821708334.dbf Completed: alter database recover managed standby database disconnect from session Media Recovery Waiting for thread 1 sequence 38272 (in transit) Mon Oct 19 18:01:33 2015 Standby controlfile consistent with primary Mon Oct 19 18:01:34 2015 Archived Log entry 5 added for thread 1 sequence 38272 ID 0xca2ab4eb dest 3: RFS[4]: Selected log 4 for thread 1 sequence 38273 dbid -903205653 branch 821708334 Mon Oct 19 18:01:39 2015 Media Recovery Log /data/oracle/oradgdata/standby_archive/1_38272_821708334.dbf Media Recovery Waiting for thread 1 sequence 38273 (in transit)

看到有ERROR信息:
Errors in file /oracle/app/oracle/diag/rdbms/pddgunq/powerdes/trace/powerdes_dbw0_14852.trc:
ORA-01186: file 201 failed verification tests
ORA-01157: cannot identify/lock data file 201 - see DBWR trace file
ORA-01110: data file 201: ‘/home/oradata/powerdes/temp01.dbf’

这种错误忽略就可以了,暂时不用考虑它们。

首页 上一页 4 5 6 7 下一页 尾页 7/7/7
】【打印繁体】【投稿】【收藏】 【推荐】【举报】【评论】 【关闭】 【返回顶部
分享到: 
上一篇MongoDB查询语句简要分析 下一篇[实验-视频过程]oracle热备份-整..

评论

帐  号: 密码: (新用户注册)
验 证 码:
表  情:
内  容: