联系：手机/微信(+86 17813235971) QQ(107644445)
标题：ORA-00600: internal error code, arguments: [4193], [35191], [35263]
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
有客户数据库由于磁盘空间满导致数据库异常,然后自行尝试强制拉库,结果数据库报ORA-00600: internal error code, arguments: [4193], [35191], [35263]错误,无法启动成功
[oracle@oracledb ~]$ sqlplus / as sysdba SQL*Plus: Release 19.0.0.0.0 - Production on Fri Jan 12 22:40:54 2024 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle. All rights reserved. Connected to an idle instance. SQL> startup mount; ORACLE instance started. Total System Global Area 1.0066E+10 bytes Fixed Size 12684768 bytes Variable Size 4261412864 bytes Database Buffers 5771362304 bytes Redo Buffers 20869120 bytes Database mounted. SQL> recover database; Media recovery complete. SQL> SQL> 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: [4193], [35191], [35263], [], [], [], [], [], [], [], [], [] Process ID: 2553131 Session ID: 862 Serial number: 11059
alert日志报错信息
2024-01-12T22:39:31.107781-05:00 Thread 1 advanced to log sequence 15 (thread open) Redo log for group 3, sequence 15 is not located on DAX storage 2024-01-12T22:39:31.113072-05:00 TT00 (PID:2558545): Gap Manager starting 2024-01-12T22:39:31.140008-05:00 Thread 1 opened at log sequence 15 Current log# 3 seq# 15 mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log Successful open of redo thread 1 2024-01-12T22:39:31.140524-05:00 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set stopping change tracking Undo initialization recovery: err:0 start: 33599386 end: 33599409 diff: 23 ms (0.0 seconds) [2553131] Successfully onlined Undo Tablespace 2. Undo initialization online undo segments: err:0 start: 33599409 end: 33599417 diff: 8 ms (0.0 seconds) Undo initialization finished serial:0 start:33599386 end:33599418 diff:32 ms (0.0 seconds) Verifying minimum file header compatibility for tablespace encryption for pdb 1.. Verifying file header compatibility for tablespace encryption completed for pdb 1 Database Characterset is AL32UTF8 2024-01-12T22:39:31.267662-05:00 ORA-00600: internal error code, arguments: [4193], [35191], [35263], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2024-01-12T22:39:31.271184-05: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. ***************************************************************** ***************************************************************** 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. ***************************************************************** Doing block recovery for file 4 block 234016 Resuming block recovery (PMON) for file 4 block 234016 Block recovery from logseq 15, block 66 to scn 0x0000000000000000 2024-01-12T22:39:31.895999-05:00 Recovery of Online Redo Log: Thread 1 Group 3 Seq 15 Reading mem 0 Mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log Block recovery completed at rba 0.0.0, scn 0x000000060fd94e6c Doing block recovery for file 4 block 144 Resuming block recovery (PMON) for file 4 block 144 Block recovery from logseq 15, block 66 to scn 0x000000060fd94ed2 2024-01-12T22:39:31.899101-05:00 Recovery of Online Redo Log: Thread 1 Group 3 Seq 15 Reading mem 0 Mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log Block recovery completed at rba 15.68.16, scn 0x000000060fd94ed3 Non-fatal internal error happened while SMON was doing shrinking of rollback segments. SMON encountered 1 out of maximum 100 non-fatal internal errors. 2024-01-12T22:39:31.960874-05:00 Errors in file /opt/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/ORCLCDB_ora_2553131.trc(incident=159324)(PDBNAME=CDB$ROOT) ORA-00600: internal error code, arguments: [4193], [35191], [35263], [], [], [], [], [], [], [], [], [] Incident details in: /opt/oracle/diag/rdbms/orclcdb/ORCLCDB/incident/incdir_159324/ORCLCDB_ora_2553131_i159324.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-12T22:39:32.042150-05: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. ***************************************************************** ***************************************************************** 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-12T22:39:32.985037-05: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. ***************************************************************** Doing block recovery for file 4 block 234016 Resuming block recovery (PMON) for file 4 block 234016 Block recovery from logseq 15, block 66 to scn 0x000000060f9df0d0 2024-01-12T22:39:33.021406-05:00 Recovery of Online Redo Log: Thread 1 Group 3 Seq 15 Reading mem 0 Mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log Block recovery completed at rba 0.0.0, scn 0x000000060fd94e6c Doing block recovery for file 4 block 144 Resuming block recovery (PMON) for file 4 block 144 Block recovery from logseq 15, block 66 to scn 0x000000060fd94ed3 2024-01-12T22:39:33.023883-05:00 Recovery of Online Redo Log: Thread 1 Group 3 Seq 15 Reading mem 0 Mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log Block recovery completed at rba 15.70.16, scn 0x000000060fd94ed4 2024-01-12T22:39:33.027444-05:00 Errors in file /opt/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/ORCLCDB_ora_2553131.trc: ORA-00600: internal error code, arguments: [4193], [35191], [35263], [], [], [], [], [], [], [], [], [] 2024-01-12T22:39:33.027525-05:00 Errors in file /opt/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/ORCLCDB_ora_2553131.trc: ORA-00600: internal error code, arguments: [4193], [35191], [35263], [], [], [], [], [], [], [], [], [] Error 600 happened during db open, shutting down database 2024-01-12T22:39:33.048575-05:00 Errors in file /opt/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/ORCLCDB_ora_2553131.trc(incident=159325)(PDBNAME=CDB$ROOT) ORA-00603: ORACLE server session terminated by fatal error ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [4193], [35191], [35263], [], [], [], [], [], [], [], [], [] Incident details in: /opt/oracle/diag/rdbms/orclcdb/ORCLCDB/incident/incdir_159325/ORCLCDB_ora_2553131_i159325.trc 2024-01-12T22:39:33.694774-05:00 opiodr aborting process unknown ospid (2553131) as a result of ORA-603 2024-01-12T22:39:33.713866-05:00 ORA-603 : opitsk aborting process License high water mark = 12 USER (ospid: (prelim)): terminating the instance due to ORA error 2024-01-12T22:39:34.734019-05:00 Instance terminated by USER(prelim), pid = 2553131
这个错误相对比较简单,一般是由于undo回滚段异常,对其进行规避,数据库open成功,然后重建新库迁移数据,完成本次恢复
