联系：手机/微信(+86 17813235971) QQ(107644445)
标题：19c库启动报ORA-600 kcbzib_kcrsds_1
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
一套19c的库由于某种情况,发现异常,当时的技术使用隐含参数强制拉库,导致数据库启动报ORA-00704 ORA-600 kcbzib_kcrsds_1错误
2024-08-24T06:11:25.494304+08:00 ALTER DATABASE OPEN 2024-08-24T06:11:25.494370+08:00 TMI: adbdrv open database BEGIN 2024-08-24 06:11:25.494324 Smart fusion block transfer is disabled: instance mounted in exclusive mode. 2024-08-24T06:11:25.515306+08:00 Beginning crash recovery of 1 threads parallel recovery started with 7 processes Thread 1: Recovery starting at checkpoint rba (logseq 2 block 3), scn 286550073 2024-08-24T06:11:25.567011+08:00 Started redo scan 2024-08-24T06:11:25.587170+08:00 Completed redo scan read 0 KB redo, 0 data blocks need recovery 2024-08-24T06:11:25.595192+08:00 Started redo application at Thread 1: logseq 2, block 3, offset 0, scn 0x0000000011146839 2024-08-24T06:11:25.595552+08:00 Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0 Mem# 0: /dbf/RLZY/redo02.log 2024-08-24T06:11:25.595712+08:00 Completed redo application of 0.00MB 2024-08-24T06:11:25.596058+08:00 Completed crash recovery at Thread 1: RBA 2.3.0, nab 3, scn 0x000000001114683a 0 data blocks read, 0 data blocks written, 0 redo k-bytes read Endian type of dictionary set to little 2024-08-24T06:11:25.648152+08:00 LGWR (PID:1614826): STARTING ARCH PROCESSES 2024-08-24T06:11:25.661738+08:00 TT00 (PID:1614908): Gap Manager starting Starting background process ARC0 2024-08-24T06:11:25.677246+08:00 ARC0 started with pid=54, OS id=1614910 2024-08-24T06:11:25.687525+08:00 LGWR (PID:1614826): ARC0: Archival started LGWR (PID:1614826): STARTING ARCH PROCESSES COMPLETE 2024-08-24T06:11:25.687733+08:00 ARC0 (PID:1614910): Becoming a 'no FAL' ARCH ARC0 (PID:1614910): Becoming the 'no SRL' ARCH 2024-08-24T06:11:25.696437+08:00 TMON (PID:1614886): STARTING ARCH PROCESSES Starting background process ARC1 2024-08-24T06:11:25.711645+08:00 Thread 1 advanced to log sequence 3 (thread open) Redo log for group 3, sequence 3 is not located on DAX storage 2024-08-24T06:11:25.715270+08:00 ARC1 started with pid=56, OS id=1614914 Starting background process ARC2 Thread 1 opened at log sequence 3 Current log# 3 seq# 3 mem# 0: /dbf/RLZY/redo03.log Successful open of redo thread 1 2024-08-24T06:11:25.728586+08:00 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Stopping change tracking 2024-08-24T06:11:25.734124+08:00 ARC2 started with pid=57, OS id=1614916 Starting background process ARC3 2024-08-24T06:11:25.752891+08:00 ARC3 started with pid=58, OS id=1614918 2024-08-24T06:11:25.752979+08:00 TMON (PID:1614886): ARC1: Archival started TMON (PID:1614886): ARC2: Archival started TMON (PID:1614886): ARC3: Archival started TMON (PID:1614886): STARTING ARCH PROCESSES COMPLETE 2024-08-24T06:11:25.802551+08:00 ARC0 (PID:1614910): Archived Log entry 2828 added for T-1.S-2 ID 0x74f18f91 LAD:1 2024-08-24T06:11:25.806845+08:00 TT03 (PID:1614922): Sleep 5 seconds and then try to clear SRLs in 2 time(s) Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc (incident=124865): ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /oracle/diag/rdbms/xff/xff/incident/incdir_124865/xff_ora_1614892_i124865.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2024-08-24T06:11:25.871925+08:00 2024-08-24T06:11:26.772652+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-08-24T06:11:26.872265+08:00 Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc: ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] 2024-08-24T06:11:26.872351+08:00 Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] 2024-08-24T06:11:26.872412+08:00 Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], [] 2024-08-24T06:11:26.872455+08:00 Error 704 happened during db open, shutting down database Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc (incident=124866): 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: /oracle/diag/rdbms/xff/xff/incident/incdir_124866/xff_ora_1614892_i124866.trc opiodr aborting process unknown ospid (1614892) as a result of ORA-603 2024-08-24T06:11:27.498146+08:00 Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc: 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], [], [], [], [], [], [], [], [], [], [], [] 2024-08-24T06:11:27.501122+08:00 ORA-603 : opitsk aborting process License high water mark = 8 USER(prelim) (ospid: 1614892): terminating the instance due to ORA error 704 2024-08-24T06:11:28.526358+08:00 Instance terminated by USER(prelim), pid = 1614892
官方关于kcbzib_kcrsds_1从解释只有:Bug 31887074 – sr21.1bigscn_hipu3 – trc – ksfdopn2 – ORA-600 [kcbzib_kcrsds_1] (Doc ID 31887074.8)
虽然关于ORA-600 [kcbzib_kcrsds_1],oracle官方没有给出来解决方案,其实通过以往大量的恢复案例和经验中已经知道,这个错误解决方案就是修改oracle scn的方法可以绕过去,以前有过一些类似恢复案例:
ORA-600 kcbzib_kcrsds_1报错
12C数据库报ORA-600 kcbzib_kcrsds_1故障处理
ORA-00603 ORA-01092 ORA-600 kcbzib_kcrsds_1
redo异常强制拉库报ORA-600 kcbzib_kcrsds_1修复
Patch SCN工具一键恢复ORA-600 kcbzib_kcrsds_1
存储故障,强制拉库报ORA-600 kcbzib_kcrsds_1处理
