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

    ORA-600 krccfl_chunk故障处理

    惜分飞发表于 2025-05-13 04:39:22
    love 0

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

    标题:ORA-600 krccfl_chunk故障处理

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

    一个数据库启动包ORA-600 krccfl_chunk错误

    2025-05-06T10:37:47.428203+08:00
    Completed: ALTER DATABASE MOUNT /* db agent *//* {2:50212:2} */
    ALTER DATABASE OPEN /* db agent *//* {2:50212:2} */
    2025-05-06T10:37:47.433709+08:00
    This instance was first to open
    Block change tracking file is current.
    Ping without log force is disabled:
      not an Exadata system.
    start recovery: pdb 0, passed in flags x4 (domain enable 5) 
    2025-05-06T10:37:48.203383+08:00
    Beginning crash recovery of 2 threads
    2025-05-06T10:37:48.568120+08:00
     parallel recovery started with 32 processes
    2025-05-06T10:37:48.610951+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.611037+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.611243+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.611438+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.614947+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.616591+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.617188+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.617253+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.617428+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.617606+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.617676+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.617809+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.636568+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.636568+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.636620+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.637156+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.637300+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.637881+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.637999+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.638112+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.638241+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.638304+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.638338+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.638347+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.641621+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.642926+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.643092+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.643192+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.643204+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.643372+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.643516+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.643573+08:00
    start recovery: pdb 0, passed in flags x5 (domain enable 5) 
    2025-05-06T10:37:48.748956+08:00
    Started redo scan
    2025-05-06T10:37:49.849382+08:00
    Completed redo scan
     read 469347 KB redo, 1213 data blocks need recovery
    2025-05-06T10:37:50.007840+08:00
    Started redo application at
     Thread 1: logseq 369323, block 651514, offset 0
     Thread 2: logseq 132962, block 1319944, offset 0
    2025-05-06T10:37:50.016910+08:00
    Recovery of Online Redo Log: Thread 1 Group 13 Seq 369323 Reading mem 0
      Mem# 0: +DATA/orcl/ONLINELOG/group_13.349.978709791
      Mem# 1: +FRA/orcl/ONLINELOG/group_13.12992.978709793
    2025-05-06T10:37:50.025725+08:00
    Recovery of Online Redo Log: Thread 2 Group 18 Seq 132962 Reading mem 0
      Mem# 0: +DATA/orcl/ONLINELOG/group_18.354.978710003
      Mem# 1: +FRA/orcl/ONLINELOG/group_18.12997.978710005
    2025-05-06T10:37:51.063556+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_ora_68031.trc(incident=868005)(PDBNAME=CDB$ROOT):
    ORA-00600: internal error code, arguments: [krccfl_chunk], [0x7F9BBB30BE58], [166528],[],[],[],[],[],[],[],[],[]
    Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl2/incident/incdir_868005/orcl2_ora_68031_i868005.trc
    2025-05-06T10:37:52.269823+08:00
    Dumping diagnostic data in directory=[cdmp_20250506103752],requested by(instance=2,osid=68031),summary=[incident=868005].
    2025-05-06T10:37:52.306517+08:00
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    2025-05-06T10:37:52.310723+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.310813+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.310820+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.310853+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.310902+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.310907+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.310945+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.310950+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.310987+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.311002+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.311009+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.311017+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.311055+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311055+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.311064+08:00
    Slave encountered ORA-10388 exception during crash recovery
    2025-05-06T10:37:52.311071+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311080+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311107+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311119+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311126+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311135+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p000_69617.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311156+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311184+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311203+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311205+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311211+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p001_69619.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311276+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p002_69621.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311276+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311280+08:00
    Recovery slave process is holding some recovery locks. Killing the instance now.
    2025-05-06T10:37:52.311308+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p003_69623.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311329+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p004_69625.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311341+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p005_69627.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311345+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p007_69631.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311353+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p008_69633.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311374+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p006_69629.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311386+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p009_69635.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311402+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p00a_69637.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311513+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p00c_69641.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.311515+08:00
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_p00b_69639.trc:
    ORA-10388: parallel query server interrupt (failure)
    2025-05-06T10:37:52.348331+08:00
    USER (ospid: 69617): terminating the instance due to error 10388
    2025-05-06T10:37:52.585589+08:00
    System state dump requested by (instance=2, osid=69617 (P000)), summary=[abnormal instance termination].
    System State dumped to trace file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_diag_67490_20250506103752.trc
    2025-05-06T10:37:54.016704+08:00
    License high water mark = 34
    2025-05-06T10:37:55.387072+08:00
    Instance terminated by USER, pid = 69617
    2025-05-06T10:37:55.388683+08:00
    Warning: 2 processes are still attach to shmid 2850830:
     (size: 45056 bytes, creator pid: 65902, last attach/detach pid: 67492)
    2025-05-06T10:37:56.018027+08:00
    USER (ospid: 69907): terminating the instance
    2025-05-06T10:37:56.021711+08:00
    Instance terminated by USER, pid = 69907
    

    查询mos发现类似文章:
    Database doesn’t open after crash ORA-00600 [krccfl_chunk] (Doc ID 2967548.1)
    Bug 33251482 – ORA-487 / ORA-600 [krccfl_chunk] : CTWR process terminated during PDB creation (Doc ID 33251482.8)
    ORA-600-krccfl_chunk


    分析这个客户情况,通过trace信息:Block change tracking file is current. 可以确认是启用了BCT,而且日志信息也反应出来是pdb环境。进一步分析客户的情况,发现他们在以前有一个数据文件创建到了本地(实际是rac环境)

    2024-12-23T11:07:09.168322+08:00
    PDBODS(5):Completed: alter tablespace PDBODS_DATA add datafile 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\USERS02.DBF'
     size 5000M autoextend on next 1000M maxsize 32000M
    

    数据库中现在实际存储路径/u01/app/oracle/product/12.2.0.1/dbhome_1/dbs/D:APPADMINISTRATORORADATAORCLUSERS 02.DBF
    基于这种情况,解决问题比较简单:在本地数据文件所在节点禁用BCT,然后open库,把数据文件拷贝到asm中即可

    • 删除redo导致ORA-00313 ORA-00312故障处理
    • 又一例ORA-600 kcratr_nab_less_than_odr
    • ORA-600 kcratr_scan_lastbwr 恢复
    • Oracle Recovery Tools修复ORA-600 6101/kdxlin:psno out of range故障
    • ORA-07445: exception encountered: core dump [expgod()+43] [IN_PAGE_ERROR]
    • 在线mv方式迁移数据文件导致数据库无法正常启动
    • pg启动报invalid checkpoint record处理
    • 虚拟机故障引起ORA-00310 ORA-00334故障处理
    • 12c启动报kcratr_nab_less_than_odr
    • Oracle Recovery Tools修复ORA-00742、ORA-600 ktbair2: illegal inheritance故障
    • .pzpq扩展名勒索恢复
    • ORA-00742 ORA-00312 故障恢复


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