IT博客汇
  • 首页
  • 精华
  • 技术
  • 设计
  • 资讯
  • 扯淡
  • 权利声明
  • 登录 注册

    ORA-600 2662

    惜分飞发表于 2016-08-01 12:19:50
    love 0

    联系:手机(13429648788) QQ(107644445)QQ咨询惜分飞

    标题:ORA-600 2662

    作者:惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

    在数据库恢复中,ORA-600 2662我想是很多人都非常熟悉的错误,下文是对于该错误的一些解释
    ORA-600 2662解释说明

    ERROR:              
    
      Format: ORA-600 [2662] [a] [b] 1 [d] [e]
     
    VERSIONS:
      versions 6.0 to 12.1
     
    DESCRIPTION:
    
      A data block SCN is ahead of the current SCN.
    
      The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN 
      stored in a UGA variable.
    
      If the SCN is less than the dependent SCN then we signal the ORA-600 [2662]
      internal error.
    
    ARGUMENTS:
      Arg [a]  Current SCN WRAP
      Arg [b]  Current SCN BASE
      Arg {c}  dependent SCN WRAP
      Arg [d]  dependent SCN BASE 
      Arg [e]  Where present this is the DBA where the dependent SCN came from.
    

    出现ORA-600 2662可能的原因

      (1) doing an open resetlogs with _ALLOW_RESETLOGS_CORRUPTION enabled    
      (2) a hardware problem, like a faulty controller, resulting in a failed 
          write to the control file or the redo logs     
      (3) restoring parts of the database from backup and not doing the 
          appropriate recovery     
      (4) restoring a control file and not doing a RECOVER DATABASE USING BACKUP 
          CONTROLFILE     
      (5) having _DISABLE_LOGGING set during crash recovery                      
      (6) problems with the DLM in a parallel server environment      
      (7) a bug   
    

    ORA-600 2662解决方法

       (1) if the SCNs in the error are very close, attempting a startup several 
           times will bump up the dscn every time we open the database even if 
           open fails. The database will open when dscn=scn.
          
       (2)You can bump the SCN either on open or while the database is open 
          using Event:ADJUST_SCN 
          Be aware that you should rebuild the database if you use this
          option.
    
    • ORA-00600 [2662]
    • 记录一次由于坏块和不恰当恢复引起各种ORA-600案例
    • 记录一次ORA-600 3004 恢复过程和处理思路
    • _ALLOW_RESETLOGS_CORRUPTION
    • ORA-38856: cannot mark instance UNNAMED_INSTANCE_2 (redo thread 2) as enabled
    • 分享一次ORA-01113 ORA-01110故障处理过程
    • 记录8.0.5数据库恢复过程
    • rac redo log file被意外覆盖数据库恢复
    • 重建控制文件
    • ORA-00600[kccpb_sanity_check_2]
    • 异常断电导致current redo损坏处理
    • 重建控制文件丢失数据文件导致悲剧


沪ICP备19023445号-2号
友情链接