重庆思庄Oracle、Redhat认证学习论坛

 找回密码
 注册

QQ登录

只需一步,快速开始

搜索
查看: 853|回复: 0
打印 上一主题 下一主题

[参考文档] Bug 16496896 - standby mrp crashed with ORA-600 [krrgv_scn8]

[复制链接]
跳转到指定楼层
楼主
发表于 2023-1-1 13:23:10 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式
本帖最后由 刘泽宇 于 2023-1-1 13:24 编辑

Symptoms:
Related To:
ORA-600 [krrgv_scn8]
(None Specified)
Description
This fix prevents media recovery on the standby from failing with
ORA-00600:[krrgv_scn8] following: a crash recovery combined with
a compatible advance on the primary database.


Rediscovery Notes
Look for:
- MRP fails with ORA-00600:[krrgv_scn8]
- RAC primary/standby (ie multiple redo threads)
- LGWR SYNC redo transport mode to the standby
- one or more redo logs have a LowSCN which is higher than their
   NextSCN, ie the following query returns some rows (the same
   rows) on the primary and the standby:
         select thread#,sequence#,first_change#,next_change#
           from v$archived_log
          where first_change# > next_change#;
- for the logs (thread#/seq#) returned by the query above, the
   primary database switched into these logs during a database
   open which performed a thread recovery coinciding with a   
   "compatible" advance, ie look for BOTH the following types
   of message in the primary database alert log as the primary
   database was opened:
     Thread <t> advanced to log sequence <s1> (thread recovery)
     Thread <t> advanced to log sequence <s2> (COMPATIBLE advance)

Workaround
To prevent the problem from happening: if compatible needs to be
changed on the primary, then only do it after a clean shutdown.
If the problem has already happened, ie the media recovery is
failing with ORA-00600:[krrgv_scn8], then there is no workaround,
ie media recovery is not possible using these logs.


分享到:  QQ好友和群QQ好友和群 QQ空间QQ空间 腾讯微博腾讯微博 腾讯朋友腾讯朋友
收藏收藏 支持支持 反对反对
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|手机版|小黑屋|重庆思庄Oracle、Redhat认证学习论坛 ( 渝ICP备12004239号-4 )

GMT+8, 2024-5-3 09:14 , Processed in 0.092895 second(s), 20 queries .

重庆思庄学习中心论坛-重庆思庄科技有限公司论坛

© 2001-2020

快速回复 返回顶部 返回列表