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

    ORA-600 kcrf_resilver_log_1故障处理

    惜分飞发表于 2024-01-18 15:36:56
    love 0

    联系:手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

    标题:ORA-600 kcrf_resilver_log_1故障处理

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

    接手一个客户的数据库故障处理,最初数据库启动报ORA-600 kcrf_resilver_log_1错

    Mon Jan 08 16:16:22 2024
    ALTER DATABASE   MOUNT
    Successful mount of redo thread 1, with mount id 2385308630
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: ALTER DATABASE   MOUNT
    Mon Jan 08 16:16:26 2024
    ALTER DATABASE OPEN
    Beginning crash recovery of 1 threads
     parallel recovery started with 15 processes
    Started redo scan
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_ora_3350.trc  (incident=276167):
    ORA-00600: internal error code, arguments: [kcrf_resilver_log_1], [0x1542C3A00], [2], , 
    Incident details in:/u2/11G/base/diag/rdbms/xff/xff/incident/incdir_276167/xff_ora_3350_i276167.trc
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Aborting crash recovery due to error 600
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_ora_3350.trc:
    ORA-00600: internal error code, arguments: [kcrf_resilver_log_1], [0x1542C3A00], [2]
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_ora_3350.trc:
    ORA-00600: internal error code, arguments: [kcrf_resilver_log_1], [0x1542C3A00], [2]
    ORA-600 signalled during: ALTER DATABASE OPEN...
    

    客户自行recover数据库之后报ORA-00283 ORA-00742 ORA-00312错

    Mon Jan 08 17:05:34 2024
    ALTER DATABASE RECOVER  database  
    Media Recovery Start
     started logmerger process
    Parallel Media Recovery started with 16 slaves
    Mon Jan 08 17:05:35 2024
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 63899 Reading mem 0
      Mem# 0: /u2/11G/data/xff/redo02.log
    Media Recovery failed with error 742
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_pr00_3857.trc:
    ORA-00283: recovery session canceled due to errors
    ORA-00742: Log read detects lost write in thread %d sequence %d block %d
    ORA-00312: online log 2 thread 1: '/u2/11G/data/xff/redo02.log'
    ORA-283 signalled during: ALTER DATABASE RECOVER  database  ...
    

    客户强制打开数据库

    Tue Jan 09 17:37:51 2024
    ALTER DATABASE OPEN
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_ora_3501.trc:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    ORA-1589 signalled during: ALTER DATABASE OPEN...
    Tue Jan 09 17:43:45 2024
    alter database open resetlogs
    RESETLOGS is being done without consistancy checks. This may result
    in a corrupted database. The database should be recreated.
    RESETLOGS after incomplete recovery UNTIL CHANGE 4418119911
    Resetting resetlogs activation ID 2289128497 (0x88715431)
    Online log /u2/11G/data/xff/redo01.log: Thread 1 Group 1 was previously cleared
    Online log /u2/11G/data/xff/redo02.log: Thread 1 Group 2 was previously cleared
    Online log /u2/11G/data/xff/redo03.log: Thread 1 Group 3 was previously cleared
    Tue Jan 09 17:43:46 2024
    Setting recovery target incarnation to 3
    Tue Jan 09 17:43:46 2024
    Assigning activation ID 2385405291 (0x8e2e656b)
    Thread 1 opened at log sequence 1
      Current log# 1 seq# 1 mem# 0: /u2/11G/data/xff/redo01.log
    Successful open of redo thread 1
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Tue Jan 09 17:43:46 2024
    SMON: enabling cache recovery
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_ora_3501.trc  (incident=492171):
    ORA-00600: internal error code, arguments: [2662], [1], [123152622], [1], [123176387], [12583040], []
    Incident details in: /u2/11G/base/diag/rdbms/xff/xff/incident/incdir_492171/xff_ora_3501_i492171.trc
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_ora_3501.trc:
    ORA-00600: internal error code, arguments: [2662], [1], [123152622], [1], [123176387], [12583040], []
    Errors in file /u2/11G/base/diag/rdbms/xff/xff/trace/xff_ora_3501.trc:
    ORA-00600: internal error code, arguments: [2662], [1], [123152622], [1], [123176387], [12583040], []
    Error 600 happened during db open, shutting down database
    USER (ospid: 3501): terminating the instance due to error 600
    Instance terminated by USER, pid = 3501
    ORA-1092 signalled during: alter database open resetlogs...
    

    这个故障相对比较简单,修改数据库scn之后,即可open数据库,然后逻辑方式迁移数据到新库即可

    • ORA-00322 ORA-00312恢复
    • ORA-00742 ORA-00312 故障恢复
    • 分享一次ORA-01113 ORA-01110故障处理过程
    • ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], []
    • Patch SCN工具快速解决ORA-600 2662问题
    • ORA-600 ksuloget2 恢复
    • ORA-600 kcbzib_kcrsds_1报错
    • ORA-15096: lost disk write detected
    • 正常open库报ORA-600 2662,ORA-600 4097错误
    • ORA-00600: internal error code, arguments: [4193], [35191], [35263]
    • ORA-00600 kcratr_scan_rc
    • commit_wait和commit_logging设置不当导致数据库无法正常启动


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