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

联系:手机/微信(+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成功,使用数据泵把数据迁移到新库,完成本次恢复(比较幸运,硬件故障的库直接迁移成功,没有报其他错误)

Oracle 19c 断电异常恢复

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

标题:Oracle 19c 断电异常恢复

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

19.3数据库由于异常断电,导致数据库无法启动,报ORA-600 ktbair2: illegal inheritance,ORA-600 6101等错误

2023-01-02T22:01:37.310225+08:00
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_pr0l_3788.trc:
ORA-10562: Error occurred while applying redo to data block (file# 10, block# 399386)
ORA-10564: tablespace DATA
ORA-01110: data file 10: 'D:\ORADATA\DATA04.ORA'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 81882
ORA-00600: internal error code, arguments: [ktbair2: illegal  inheritance], [], [], [], [], [], [], [], [], [], [], []
2023-01-02T22:01:37.544630+08:00
Slave exiting with ORA-10562 exception
2023-01-02T22:01:37.560258+08:00
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_pr03_4364.trc:
ORA-10562: Error occurred while applying redo to data block (file# 2, block# 716430)
ORA-10564: tablespace DATA
ORA-01110: data file 2: 'D:\ORADATA\DATA01.ORA'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 81743
ORA-00600: internal error code, arguments: [6101], [0], [16], [0], [0], [0], [], [], [], [], [], []
2023-01-02T22:01:38.294726+08:00
Slave exiting with ORA-10562 exception
2023-01-02T22:01:38.310354+08:00
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_pr0e_5980.trc:
ORA-10562: Error occurred while applying redo to data block (file# 2, block# 714911)
ORA-10564: tablespace DATA
ORA-01110: data file 2: 'D:\ORADATA\DATA01.ORA'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 74014
ORA-00600: internal error code, arguments: [ktbair2: illegal  inheritance], [], [], [], [], [], [], [], [], [], [], []
2023-01-02T22:01:48.921092+08:00
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_pr00_4760.trc:
ORA-00283: recovery session canceled due to errors
ORA-00448: normal completion of background process
2023-01-02T22:01:49.171125+08:00
ORA-756 signalled during: ALTER DATABASE RECOVER  database  ...

报错比较明显由于redo和datafile不匹配导致recover 不成功,尝试强制拉库

SQL> alter database open resetlogs ;
alter database open resetlogs 
*
第 1 行出现错误:
ORA-00603: ORACLE server session terminated by fatal error
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [],
[], [], [], [], [], [], []
进程 ID: 6068
会话 ID: 3631 序列号: 54960
Undo initialization recovery: err:600 start: 20760593 end: 20762484 diff: 1891 ms (1.9 seconds)
2023-01-02T22:09:05.539709+08:00
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_6068.trc:
ORA-00600: 内部错误代码, 参数: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
2023-01-02T22:09:05.555336+08:00
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_6068.trc:
ORA-00600: 内部错误代码, 参数: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_6068.trc  (incident=293955):
ORA-00603: ORACLE 服务器会话因致命错误而终止
ORA-01092: ORACLE 实例终止。强制断开连接
ORA-00600: 内部错误代码, 参数: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\incident\incdir_293955\orcl_ora_6068_i293955.trc
2023-01-02T22:09:06.805497+08:00
opiodr aborting process unknown ospid (6068) as a result of ORA-603
2023-01-02T22:09:06.961768+08:00
ORA-603 : opitsk aborting process

参考类似处理open数据库成功:
ORA-600 kcbzib_kcrsds_1报错
12C数据库报ORA-600 kcbzib_kcrsds_1故障处理
redo异常强制拉库报ORA-600 kcbzib_kcrsds_1修复
ORA-00603 ORA-01092 ORA-600 kcbzib_kcrsds_1

redo异常强制拉库报ORA-600 kcbzib_kcrsds_1修复

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

标题:redo异常强制拉库报ORA-600 kcbzib_kcrsds_1修复

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

节点2 asm dismount导致redo写报错(ORA-00340,ORA-00345),经过分析asm和系统日志,确认是由于多路径异常导致io异常

2022-01-24T23:44:39.966602+08:00
WARNING: group 4 is being dismounted.
WARNING: ASMB force dismounting group 4 (REDO) due to ASM server dismount
SUCCESS: diskgroup REDO was dismounted
2022-01-24T23:44:41.103783+08:00
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF2/trace/XFF2_lgwr_228507.trc:
ORA-00345: redo log write error block 11961764 count 6
ORA-00312: online log 10 thread 2: '+REDO/XFF/ONLINELOG/group_10.261.1074690685'
2022-01-24T23:44:41.156809+08:00
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF2/trace/XFF2_lgwr_228507.trc:
ORA-00340: IO error processing online log 10 of thread 2
ORA-00345: redo log write error block 11961764 count 6
ORA-00312: online log 10 thread 2: '+REDO/XFF/ONLINELOG/group_10.261.1074690685'
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF2/trace/XFF2_lgwr_228507.trc  (incident=1341402):
ORA-340 [] [] [] [] [] [] [] [] [] [] [] []
Incident details in: /u01/app/oracle/diag/rdbms/xff/XFF2/incident/incdir_1341402/XFF2_lgwr_228507_i1341402.trc
2022-01-24T23:44:41.505251+08:00
USER (ospid: 133928): terminating the instance due to error 340

由于节点2是突然crash,节点1做实例恢复失败,由于节点2的redo发生了写丢失,导致节点1实例恢复后库crash,进而是的该集群的相关数据库节点全部crash

2022-01-24T23:46:08.440519+08:00
Slave encountered ORA-10388 exception during crash recovery
2022-01-24T23:46:08.442854+08:00
Slave encountered ORA-10388 exception during crash recovery
Abort recovery for domain 0, flags 4
2022-01-24T23:46:08.444531+08:00
Aborting crash recovery due to error 742
2022-01-24T23:46:08.444695+08:00
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF1/trace/XFF1_ora_450481.trc:
ORA-00742: Log read detects lost write in thread 2 sequence 63507 block 11941482
ORA-00312: online log 10 thread 2: '+REDO/XFF/ONLINELOG/group_10.261.1074690685'
Abort recovery for domain 0, flags 4
2022-01-24T23:46:08.771108+08:00
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF1/trace/XFF1_ora_450481.trc:
ORA-00742: Log read detects lost write inthread 2 sequence 63507 block 11941482
ORA-00312: online log 10 thread 2: '+REDO/XFF/ONLINELOG/group_10.261.1074690685'
ORA-742 signalled during: ALTER DATABASE OPEN /* db agent *//* {0:17:165} */...
2022-01-24T23:46:10.143155+08:00
License high water mark = 33
2022-01-24T23:46:10.143752+08:00
USER (ospid: 451049): terminating the instance
2022-01-24T23:46:11.167337+08:00
Instance terminated by USER, pid = 451049

经过第三方强制拉库之后,数据库报ORA-600 kcbzib_kcrsds_1

2022-01-25T10:13:37.922332+08:00
Completed crash recovery at
 Thread 2: RBA 5.3.16, nab 3, scn 0x00000a348a032122
 0 data blocks read, 0 data blocks written, 0 redo k-bytes read
2022-01-25T10:13:38.071326+08:00
Thread 2 advanced to log sequence 6 (thread recovery)
validate pdb 0, flags x4, valid 0, pdb flags x204 
* validated domain 0, flags = 0x200
CRASH recovery complete: pdb 0 valid 1 (flags x4, pdb flags x200) 
Picked broadcast on commit scheme to generate SCNs
Endian type of dictionary set to little
2022-01-25T10:13:38.389741+08:00
TT00: Gap Manager starting (PID:220505)
2022-01-25T10:13:38.646484+08:00
Thread 1 opened at log sequence 1
  Current log# 1 seq# 1 mem# 0: +DATA/XFF/ONLINELOG/group_1.536.1094875107
Successful open of redo thread 1
2022-01-25T10:13:38.647243+08:00
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF1/trace/XFF1_ora_216590.trc  (incident=1879556):
ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/xff/XFF1/incident/incdir_1879556/XFF1_ora_216590_i1879556.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
*****************************************************************
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.
*****************************************************************
2022-01-25T10:13:39.734366+08:00
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF1/trace/XFF1_ora_216590.trc:
ORA-00704: bootstrap process failure
ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
2022-01-25T10:13:39.734424+08:00
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF1/trace/XFF1_ora_216590.trc:
ORA-00704: bootstrap process failure
ORA-00704: bootstrap process failure
ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
2022-01-25T10:13:39.734499+08:00
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF1/trace/XFF1_ora_216590.trc:
ORA-00704: bootstrap process failure
ORA-00704: bootstrap process failure
ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
2022-01-25T10:13:39.734536+08:00
Error 704 happened during db open, shutting down database
Errors in file /u01/app/oracle/diag/rdbms/xff/XFF1/trace/XFF1_ora_216590.trc  (incident=1879557):
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/XFF1/incident/incdir_1879557/XFF1_ora_216590_i1879557.trc
2022-01-25T10:13:39.894464+08:00
2022-01-25T10:13:40.446888+08:00
opiodr aborting process unknown ospid (216590) as a result of ORA-603
2022-01-25T10:13:40.470643+08:00
ORA-603 : opitsk aborting process
License high water mark = 36
2022-01-25T10:13:40.471453+08:00
USER (ospid: 216590): terminating the instance due to error 704
2022-01-25T10:13:41.436133+08:00
opiodr aborting process unknown ospid (189796) as a result of ORA-1092
2022-01-25T10:13:41.439011+08:00
ORA-1092 : opitsk aborting process
2022-01-25T10:13:41.472060+08:00
PMON (ospid: 189585): terminating the instance due to error 704

该错误是12c之后才有的报错,由于文件异常导致,通过以前的解决经验,接手这个问题之后快速调整数据库文件头信息,顺利open库
参考以前相关blog内容:
Oracle 12c redo 丢失恢复
模拟19c数据库redo异常恢复
ORA-600 kcbzib_kcrsds_1报错
12C数据库报ORA-600 kcbzib_kcrsds_1故障处理
ORA-00603 ORA-01092 ORA-600 kcbzib_kcrsds_1

[oracle@xifenfei02 ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Wed Jan 26 00:31:50 2022

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup mount pfile='/tmp/pfile'
ORACLE instance started.

Total System Global Area 3.2320E+11 bytes
Fixed Size                 29879248 bytes
Variable Size            4.5634E+10 bytes
Database Buffers         1.9059E+11 bytes
Redo Buffers             1043861504 bytes
In-Memory Area           8.5899E+10 bytes
Database mounted.
SQL> alter database open ;

Database altered.

ORA-00603 ORA-01092 ORA-600 kcbzib_kcrsds_1

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

标题:ORA-00603 ORA-01092 ORA-600 kcbzib_kcrsds_1

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

接手客户故障数据库报错为:ORA-16433

[orauser@xifenfei check_db]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Tue Dec 14 02:36:24 2021

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> alter database backup controlfile to trace as '/tmp/ctl';
alter database backup controlfile to trace as '/tmp/ctl'
*
ERROR at line 1:
ORA-16433: The database or pluggable database must be opened in read/write mode.


SQL> recover datafile 1;
ORA-00283: recovery session canceled due to errors
ORA-16433: The database or pluggable database must be opened in read/write mode.

这个错误一般是由于之前resetlogs未能正常打开库导致,通过rectl之后,尝试重新打开库,报错为:ORA-600 kcbzib_kcrsds_1

SQL> ALTER DATABASE OPEN;
ALTER DATABASE OPEN
*
ERROR at line 1:
ORA-00603: ORACLE server session terminated by fatal error
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []
Process ID: 49304
Session ID: 4698 Serial number: 14852

这个错误一般是scn问题,对于之前版本直接使用隐含参数,event,oradebug进行调整scn即可,但是在12.2版本之后无法使用这些方法修改,处理起来相对麻烦一些,参考以前处理的相关文章:
ORA-600 kcbzib_kcrsds_1报错
12C数据库报ORA-600 kcbzib_kcrsds_1故障处理
oradebug poke ORA-32521/ORA-32519故障解决

12C数据库报ORA-600 kcbzib_kcrsds_1故障处理

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

标题:12C数据库报ORA-600 kcbzib_kcrsds_1故障处理

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

有朋友由于主机断电,导致数据库无法启动,需要我们提供恢复支持.通过Oracle数据库异常恢复检查脚本(Oracle Database Recovery Check)检查分析,发现存放在一个磁盘的数据文件scn过小,数据库无法正常open,需要历史redo(已经被覆盖,而且数据库未归档).
20201130202509
20201130202545


对于这种情况,选择强制拉库,然后数据库报ORA-600 kcbzib_kcrsds_1错误
20201130203023
20201130203204

对于此类故障参考以前处理过类似案例:ORA-600 kcbzib_kcrsds_1报错,对数据库scn进行修改,数据库顺利open
20201130203529