首页 > 其他分享 >存储故障,强制拉库报ORA-600 kcbzib_kcrsds_1处理---惜分飞

存储故障,强制拉库报ORA-600 kcbzib_kcrsds_1处理---惜分飞

时间:2024-01-19 21:26:09浏览次数:26  
标签:00 01 600 kcbzib XFFPDB 分飞 XFF 2024 ORA

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

标题:存储故障,强制拉库报ORA-600 kcbzib_kcrsds_1处理

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

硬件故障,客户自行强制resetlogs库,报ORA-600 kcbzib_kcrsds_1错误

2024-01-17T17:30:33.094367+08:00 alter database open resetlogs 2024-01-17T17:30:33.105461+08:00 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 16456823130015 time .... (PID:1584): Clearing online redo logfile 1 /u01/app/oracle/oradata/XFF/redo01.log .... (PID:1584): Clearing online redo logfile 2 /u01/app/oracle/oradata/XFF/redo02.log .... (PID:1584): Clearing online redo logfile 3 /u01/app/oracle/oradata/XFF/redo03.log Clearing online log 1 of thread 1 sequence number 1345 Clearing online log 2 of thread 1 sequence number 1346 Clearing online log 3 of thread 1 sequence number 1347 2024-01-17T17:30:43.054150+08:00 .... (PID:1584): Clearing online redo logfile 1 complete .... (PID:1584): Clearing online redo logfile 2 complete .... (PID:1584): Clearing online redo logfile 3 complete Resetting resetlogs activation ID 259120030 (0xf71db9e) Online log /u01/app/oracle/oradata/XFF/redo01.log: Thread 1 Group 1 was previously cleared Online log /u01/app/oracle/oradata/XFF/redo02.log: Thread 1 Group 2 was previously cleared Online log /u01/app/oracle/oradata/XFF/redo03.log: Thread 1 Group 3 was previously cleared 2024-01-17T17:30:43.201042+08:00 Setting recovery target incarnation to 3 2024-01-17T17:30:43.267669+08:00 Smart fusion block transfer is disabled:   instance mounted in exclusive mode. 2024-01-17T17:30:43.282033+08:00 Crash Recovery excluding pdb 2 which was cleanly closed. Endian type of dictionary set to little 2024-01-17T17:30:43.396061+08:00 Assigning activation ID 280673168 (0x10babb90) Redo log for group 1, sequence 1 is not located on DAX storage 2024-01-17T17:30:43.433441+08:00 TT00 (PID:1652): Gap Manager starting 2024-01-17T17:30:43.526972+08:00 Thread 1 opened at log sequence 1   Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/XFF/redo01.log Successful open of redo thread 1 2024-01-17T17:30:43.528058+08:00 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Stopping change tracking 2024-01-17T17:30:44.097557+08:00 Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_1584.trc(incident=263984)(PDBNAME=CDB$ROOT): ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/XFF/XFF/incident/incdir_263984/XFF_ora_1584_i263984.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2024-01-17T17:30:47.913013+08:00 ***************************************************************** An internal routine has requested a dump of selected redo. This usually happens following a specific internal error, when analysis of the redo logs will help Oracle Support with the diagnosis. It is recommended that you retain all the redo logs generated (by all the instances) during the past 12 hours, in case additional redo dumps are required to help with the diagnosis. ***************************************************************** 2024-01-17T17:30:48.228934+08:00 Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_1584.trc: ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] 2024-01-17T17:30:48.229250+08:00 Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_1584.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] 2024-01-17T17:30:48.229572+08:00 Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_1584.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] Error 704 happened during db open, shutting down database Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_1584.trc  (incident=263985) (PDBNAME=CDB$ROOT): ORA-00603: ORACLE server session terminated by fatal error ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/XFF/XFF/incident/incdir_263985/XFF_ora_1584_i263985.trc 2024-01-17T17:30:50.982998+08:00 opiodr aborting process unknown ospid (1584) as a result of ORA-603 2024-01-17T17:30:50.989089+08:00 ORA-603 : opitsk aborting process

这个错误处理过多次一般是由于scn异常导致,以前部分类似文章
ORA-600 kcbzib_kcrsds_1报错
12C数据库报ORA-600 kcbzib_kcrsds_1故障处理
redo异常强制拉库报ORA-600 kcbzib_kcrsds_1修复
Patch SCN工具一键恢复ORA-600 kcbzib_kcrsds_1
处理好该错误之后,数据库在open pdb的时候报ORA-600 4193错误

2024-01-18T09:59:18.211131+08:00 alter pluggable database all open 2024-01-18T09:59:18.213569+08:00 XFFPDB(4):Pluggable database XFFPDB opening in read write 2024-01-18T09:59:18.590332+08:00 QPI: opatch file present, opatch QPI: qopiprep.bat file present 2024-01-18T09:59:18.701197+08:00 XFFPDB(4):SUPLOG: Initialize PDB SUPLOG SGA, old value 0x0, new value 0x18 XFFPDB(4):Autotune of undo retention is turned on. XFFPDB(4):Endian type of dictionary set to little 2024-01-18T09:59:18.842283+08:00 Buffer Cache Full DB Caching mode changing from FULL CACHING ENABLED to FULL CACHING DISABLED Full DB Caching disabled: DEFAULT_CACHE_SIZE should be at least 153531 MBs bigger than current size. 2024-01-18T09:59:19.017859+08:00 XFFPDB(4):Undo initialization recovery: Parallel FPTR failed: start:233023254 end:233023260 diff:6 ms(0.0 seconds) XFFPDB(4):Undo initialization recovery: err:0 start: 233023254 end: 233023286 diff: 32 ms (0.0 seconds) 2024-01-18T09:59:19.256942+08:00 XFFPDB(4):[2475] Successfully onlined Undo Tablespace 40. XFFPDB(4):Undo initialization online undo segments: err:0 start: 233023286 end: 233023500 diff:214 ms(0.2 seconds) XFFPDB(4):Undo initialization finished serial:0 start:233023228 end:233023508 diff:280 ms (0.3 seconds) XFFPDB(4):Database Characterset for XFFPDB is ZHS16GBK XFFPDB(4):********************************************************************* XFFPDB(4):WARNING: The following temporary tablespaces in container(XFFPDB) XFFPDB(4):         contain no files. XFFPDB(4):         This condition can occur when a backup controlfile has XFFPDB(4):         been restored.  It may be necessary to add files to these XFFPDB(4):         tablespaces.  That can be done using the SQL statement: XFFPDB(4): XFFPDB(4):         ALTER TABLESPACE <tablespace_name> ADD TEMPFILE XFFPDB(4): XFFPDB(4):         Alternatively, if these temporary tablespaces are no longer XFFPDB(4):         needed, then they can be dropped. XFFPDB(4):           Empty temporary tablespace: TEMP XFFPDB(4):********************************************************************* Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_2475.trc  (incident=392032) (PDBNAME=XFFPDB): ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] XFFPDB(4):Incident details in:/u01/app/oracle/diag/rdbms/XFF/XFF/incident/incdir_392032/XFF_ora_2475_i392032.trc XFFPDB(4):Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2024-01-18T09:59:20.079597+08:00 XFFPDB(4):***************************************************************** XFFPDB(4):An internal routine has requested a dump of selected redo. XFFPDB(4):This usually happens following a specific internal error, when XFFPDB(4):analysis of the redo logs will help Oracle Support with the XFFPDB(4):diagnosis. XFFPDB(4):It is recommended that you retain all the redo logs generated (by XFFPDB(4):all the instances) during the past 12 hours, in case additional XFFPDB(4):redo dumps are required to help with the diagnosis. XFFPDB(4):***************************************************************** =========================================================== Dumping current patch information =========================================================== Unable to obtain current patch information due to error: 20001 =========================================================== 2024-01-18T09:59:31.793666+08:00 XFFPDB(4):Flush retried for xcb 0x179400620, pmd 0x174a2f6c0 XFFPDB(4):Doing block recovery for file 31 block 1239 2024-01-18T09:59:31.805351+08:00 Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_2475.trc  (incident=392034)(PDBNAME=XFFPDB): ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] XFFPDB(4):Incident details in:/u01/app/oracle/diag/rdbms/XFF/XFF/incident/incdir_392034/XFF_ora_2475_i392034.trc XFFPDB(4):Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2024-01-18T09:59:32.009996+08:00 XFFPDB(4):***************************************************************** XFFPDB(4):An internal routine has requested a dump of selected redo. XFFPDB(4):This usually happens following a specific internal error, when XFFPDB(4):analysis of the redo logs will help Oracle Support with the XFFPDB(4):diagnosis. XFFPDB(4):It is recommended that you retain all the redo logs generated (by XFFPDB(4):all the instances) during the past 12 hours, in case additional XFFPDB(4):redo dumps are required to help with the diagnosis. XFFPDB(4):***************************************************************** Incident details in: /u01/app/oracle/diag/rdbms/XFF/XFF/incident/incdir_392384/XFF_mz00_2879_i392384.trc 2024-01-18T09:59:36.918296+08:00 Reread of blocknum=142165, file=/u01/app/oracle/oradata/XFF/system01.dbf. found same corrupt data Reread of blocknum=142165, file=/u01/app/oracle/oradata/XFF/system01.dbf. found same corrupt data Reread of blocknum=142165, file=/u01/app/oracle/oradata/XFF/system01.dbf. found same corrupt data Reread of blocknum=142165, file=/u01/app/oracle/oradata/XFF/system01.dbf. found same corrupt data Reread of blocknum=142165, file=/u01/app/oracle/oradata/XFF/system01.dbf. found same corrupt data 2024-01-18T09:59:41.146850+08:00 XFFPDB(4):Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_2475.trc: ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] 2024-01-18T09:59:45.434605+08:00 Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_2475.trc  (incident=407714): ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/XFF/XFF/incident/incdir_407714/XFF_ora_2475_i407714.trc 2024-01-18T09:59:45.439083+08:00 Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/incident/incdir_407714/XFF_ora_2475_i407714.trc: ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4193], [14648], [14652], [], [], [], [], [], [], [], [], [] 2024-01-18T09:59:48.575971+08:00 XFFPDB(4):pdb open recovery: pdbid=4 log=255 acquired_ip=1

这个相对比较简单,对异常undo进行处理,cdb和pdb都open成功,使用数据泵把数据迁移到新库,完成本次恢复(比较幸运,硬件故障的库直接迁移成功,没有报其他错误)

标签:00,01,600,kcbzib,XFFPDB,分飞,XFF,2024,ORA
From: https://www.cnblogs.com/xifenfei/p/17975636

相关文章

  • 基于TIC6000 DSP教学实验箱_数字图像处理操作教程:5-20 图像离散余弦变换(LCD显示)
    一、实验目的学习图像离散余弦变换的原理,掌握图像的读取方法,并实现在LCD上显示余弦变换前后的图像。二、实验原理图像离散余弦变换图像的离散余弦变换广泛用于图像的压缩。对原始图像进行离散余弦变换,变换后DCT系数能量主要集中在左上角,其余大部分系数接近于零,DCT具有适用于图像压......
  • 尊嘟假嘟?三行代码提升接口性能600倍
    一、背景  业务在群里反馈编辑结算单时有些账单明细查不出来,但是新建结算单可以,我第一反应是去测试环境试试有没有该问题,结果发现没任何问题!!!  然后我登录生产环境编辑业务反馈有问题的结算单,发现查询接口直接504网关超时了,此时心里已经猜到是代码性能问题导致的,接来下就把重......
  • 基于TIC6000的DSP教学实验箱操作教程:5-18 RGB24图像灰度转换(LCD显示)
    一、实验目的学习RGB24图像灰度转换的原理,掌握图像的读取方法,并实现在LCD上显示灰度转换前后的图像。二、实验原理RGB24图像灰度转换RGB颜色空间作为一种常用的彩色图像表示模型,分别用红(R)、绿(G)、蓝(B)三原色的组合来表示每个像素的颜色。一般情况下,RGB彩色图像灰度化有三种转化方案:(1)......
  • 疾速7600MT/s!KELVV科赋CRAS V RGB DDR5内存图赏
    12月18日消息,KLEVV科赋日前推出新款大容量DDR5内存套装,满足游戏玩家、内容创作者和高端PC爱好者的需求。现在,KLEVV科赋CRASVRGB内存套装已经来到我们评测室,下面为大家带来图赏。目前在售CRASVRGB均为16B*2套装,提供6000MT/s、6400MT/s、7200MT/s、7600MT/s、8000MT/s共五种不同......
  • 《安富莱嵌入式周报》第329期:圣诞前夕,各种软件井喷式更新,开源600Wh的UPS低压电源,各种
    周报汇总地址:http://www.armbbs.cn/forum.php?mod=forumdisplay&fid=12&filter=typeid&typeid=104 圣诞前夕,各种软件井喷式发布新版本视频版:https://www.bilibili.com/video/BV19Q4y1u7Es 1、开源600Wh的UPS低压电源https://pop.fsck.pl/projects/secondlife-ups-Mk......
  • 实验六_OOP_张文瑞_202213260018
    实验任务4Vector.hpp源代码1#include<iostream>2#include<stdexcept>34template<typenameT>5classVector{6private:7intsize;8T*vec;9public:10Vector<T>()=default;11......
  • SFP6006-ASEMI新能源功率器件SFP6006
    编辑:llSFP6006-ASEMI新能源功率器件SFP6006型号:SFP6006品牌:ASEMI封装:TO-247最大平均正向电流:60A最大重复峰值反向电压:600V产品引线数量:3产品内部芯片个数:2产品内部芯片尺寸:140MIL峰值正向漏电流:<10ua恢复时间:35ns浪涌电流:600A芯片材质:最大正向电压:0.98V~1.90V工作......
  • mysql数据库文件丢失恢复---惜分飞
    联系:手机/微信(+8617813235971)QQ(107644445)标题:mysql数据库文件丢失恢复作者:惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]客户服务器重启,mysql相关数据文件丢失通过底层工具进行分析,无法正确恢复数据库名字,一个个单个ibd文件(......
  • PCIe 4.0天花板级性能!致态Ti600 4TB固态硬盘上手
    沉寂已久的固态硬盘市场终于迎来了破局者,长江存储·致态在TiPlus7100固态硬盘一炮走红之后,继续对产品进行迭代,并在今年10月推出了Ti系列的首款产品——致态Ti600固态硬盘。致态Ti600固态硬盘拥有更高的性价比,针对不同玩家提供了500GB,1TB及2TB多个容量版本,同时在性能方面丝毫不含......
  • 1299元!一图看懂长江存储致态Ti600 4TB超大杯
    今天,长江存储旗下致态正式发布了Ti6004TB大容量版本的SSD,目前已在京东和天猫官方旗舰店开售,价格为1299元。致态Ti6004TB容量版本采用了基于长江存储晶栈Xtacking3.0架构的QLC原厂颗粒,支持PCIe4.0、NVMe2.0协议,顺序读速达到了7000MB/s,顺序写入速度为6000MB/s。而且在晶栈Xtack......