记一次Oracle REDO在线日志损坏故障修复
数据库告警日志从Sat Apr 11 18:33:41 2026出现redo1日志 error block 坏块
Sat Apr 11 18:33:41 2026
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_lgwr_73863.trc:
ORA-00345: redo log write error block 18103 count 2
ORA-00312: online log 1 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo01.log'
ORA-27072: File I/O error
Linux-x86_64 Error: 11: Resource temporarily unavailable
Additional information: 4
Additional information: 18103
Additional information: 512
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_lgwr_73863.trc:
ORA-00340: IO error processing online log 1 of thread 1
ORA-00345: redo log write error block 18103 count 2
ORA-00312: online log 1 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo01.log'
ORA-27072: File I/O error
Linux-x86_64 Error: 11: Resource temporarily unavailable
Additional information: 4
Additional information: 18103
Additional information: 512
LGWR (ospid: 73863): terminating the instance due to error 340
Instance terminated by LGWR, pid = 73863
Sat Apr 11 19:49:47 2026查看是当前日志文件损坏
SQL> select group#,sequence#,archived,status from v$log;
GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
1 112804 NO CURRENT
3 112803 NO INACTIVE
2 112802 NO INACTIVE
SQL> 查看操作系统日志发现从Apr 11 18:33:40 开始出现磁盘告警
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: megaraid_sas 0000:03:00.0: 8179 (829217946s/0x0001/FATAL) - Uncorrectable medium error logged for VD 00/0 at 80ffe9 (on PD 01(e0x20/s1) at 80ffe9)
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: scsi_io_completion: 27 callbacks suppressed
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Sense Key : Medium Error [current]
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Add. Sense: No additional sense information
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 80 ff e8 00 00 08 00
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: blk_update_request: 27 callbacks suppressed
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: blk_update_request: I/O error, dev sda, sector 8454120
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Sense Key : Medium Error [current]
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Add. Sense: No additional sense information
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 80 ff e8 00 00 08 00
Apr 11 18:33:40 SPS-StorageSer-133-11 kernel: blk_update_request: I/O error, dev sda, sector 8454120
Apr 11 18:34:26 SPS-StorageSer-133-11 systemd: Started Session c765916 of user root.
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Sense Key : Medium Error [current]
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Add. Sense: No additional sense information
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 80 ff e8 00 00 08 00
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: blk_update_request: I/O error, dev sda, sector 8454120
Apr 11 19:49:56 SPS-StorageSer-133-11 kernel: Buffer I/O error on dev dm-0, logical block 794109, async page read
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#1 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Sense Key : Medium Error [current]
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 Add. Sense: No additional sense information
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: sd 0:2:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 80 ff e8 00 00 08 00
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: blk_update_request: I/O error, dev sda, sector 8454120
Apr 11 19:49:57 SPS-StorageSer-133-11 kernel: Buffer I/O error on dev dm-0, logical block 794109, async page read
Apr 11 19:50:01 SPS-StorageSer-133-11 systemd: Started Session 162186 of user root.尝试重启数据库再次报错
Completed: ALTER DATABASE MOUNT
Sat Apr 11 19:49:55 2026
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 5 processes
Started redo scan
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_10318.trc:
ORA-00333: redo log read error block 16875 count 6144
ORA-00312: online log 1 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo01.log'
ORA-27072: File I/O error
Linux-x86_64 Error: 25: Inappropriate ioctl for device
Additional information: 4
Additional information: 16875
Additional information: 629248
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_10318.trc:
ORA-00333: redo log read error block 14827 count 8192
ORA-00312: online log 1 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo01.log'
ORA-27072: File I/O error
Linux-x86_64 Error: 25: Inappropriate ioctl for device
Additional information: 4
Additional information: 14827
Additional information: 1677824
Aborting crash recovery due to error 333
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_10318.trc:
ORA-00333: redo log read error block 14827 count 8192
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_10318.trc:
ORA-00333: redo log read error block 14827 count 8192
ORA-333 signalled during: ALTER DATABASE OPEN...
Sat Apr 11 19:58:02 2026
Shutting down instance (abort)多次尝试重启数据库均失败了
Sat Apr 11 20:36:08 2026
alter database open
Beginning crash recovery of 1 threads
parallel recovery started with 5 processes
Started redo scan
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_72238.trc:
ORA-00333: redo log read error block 16875 count 6144
ORA-00312: online log 1 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo01.log'
ORA-27072: File I/O error
Linux-x86_64 Error: 25: Inappropriate ioctl for device
Additional information: 4
Additional information: 16875
Additional information: 629248
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_72238.trc:
ORA-00333: redo log read error block 14827 count 8192
ORA-00312: online log 1 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo01.log'
ORA-27072: File I/O error
Linux-x86_64 Error: 25: Inappropriate ioctl for device
Additional information: 4
Additional information: 14827
Additional information: 1677824
Aborting crash recovery due to error 333
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_72238.trc:
ORA-00333: redo log read error block 14827 count 8192
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_72238.trc:
ORA-00333: redo log read error block 14827 count 8192
ORA-333 signalled during: alter database open...
Sat Apr 11 20:37:35 2026
alter database open尝试修改隐含参数再次以resetlogs重启数据库 ，但是出现了ORA-00600的错误
-- 1. 在 init.ora 或 spfile 中添加隐藏参数
ALTER SYSTEM SET "_allow_resetlogs_corruption"=TRUE SCOPE=SPFILE;
-- 2. 重启数据库到 mount 状态
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
-- 3. 执行基于取消的恢复
RECOVER DATABASE UNTIL CANCEL; -- 输入 CANCEL
-- 4. 强制打开数据库
ALTER DATABASE OPEN RESETLOGS;第一次出现ORA00600 2662错误
ORA-00600: internal error code, arguments: [2662], [1], [451386466], [1], [451414602], [12583040], [], [], [], [], [], []
数据库损坏之后，使用_allow_resetlogs_corruption 不一定能打开。也会出现以下的问题。其中[2662]代表的意思如下：ORA-600 [2662]"Block sCN is ahead of Current SCN
说明当前数据库的数据块保存的SCN大于当前的SCN，因为Current SCN会和dependent SCN进行比比较。如果[Current SCN] <[dependent SCN]，那么数据库就会产生这个ORA-600[2662]的错误了。这个错误一共有五个参数，分别代表不同的含义,
ORA-600 [2662] [a] [b] [c] [d] [e]
Arg [a] Current SCN WRAP
Arg [b]Current SCN BASE
Arg [c] dependent SCN WRAP
Arg [d] dependent SCN BASE(数据库块的SCN)
每次尝试重启数据库的时候SCN号会推进一次
Sat Apr 11 20:59:27 2026
ALTER DATABASE RECOVER DATABASE UNTIL CANCEL
Media Recovery Start
started logmerger process
Parallel Media Recovery started with 6 slaves
ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL CANCEL ...
ALTER DATABASE RECOVER CANCEL
Sat Apr 11 20:59:30 2026
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_pr00_58918.trc:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/app/oracle/product/oradata/orcl11g/system01.dbf'
Slave exiting with ORA-1547 exception
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_pr00_58918.trc:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/app/oracle/product/oradata/orcl11g/system01.dbf'
ORA-10879 signalled during: ALTER DATABASE RECOVER CANCEL ...
ALTER DATABASE RECOVER CANCEL
Media Recovery Canceled
Completed: ALTER DATABASE RECOVER CANCEL
Sat Apr 11 20:59:39 2026
ALTER DATABASE OPEN RESETLOGS
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 4746353752
Resetting resetlogs activation ID 1111585933 (0x4241748d)
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc:
ORA-00367: checksum error in log file header
ORA-00322: log 1 of thread 1 is not current copy
ORA-00312: online log 1 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo01.log'
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc:
ORA-00367: checksum error in log file header
ORA-00322: log 2 of thread 1 is not current copy
ORA-00312: online log 2 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo02.log'
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc:
ORA-00367: checksum error in log file header
ORA-00322: log 3 of thread 1 is not current copy
ORA-00312: online log 3 thread 1: '/opt/app/oracle/product/oradata/orcl11g/redo03.log'
Sat Apr 11 20:59:50 2026
Setting recovery target incarnation to 3
Sat Apr 11 20:59:50 2026
Assigning activation ID 1337200926 (0x4fb4111e)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /opt/app/oracle/product/oradata/orcl11g/redo01.log
Successful open of redo thread 1
Sat Apr 11 20:59:51 2026
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sat Apr 11 20:59:51 2026
SMON: enabling cache recovery
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc (incident=135753):
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_135753/orcl11g_ora_31992_i135753.trc
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc:
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc:
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER (ospid: 31992): terminating the instance due to error 600
Instance terminated by USER, pid = 31992
ORA-1092 signalled during: ALTER DATABASE OPEN RESETLOGS...
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc (incident=135754):
ORA-00600: internal error code, arguments: [2662], [1], [451386466], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_135754/orcl11g_ora_31992_i135754.trc
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc (incident=135755):
ORA-00600: internal error code, arguments: [2662], [1], [451386467], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [1], [451386466], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_135755/orcl11g_ora_31992_i135755.trc
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc:
ORA-00600: internal error code, arguments: [2662], [1], [451386467], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [1], [451386466], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc:
ORA-27300: OS system dependent operation:semctl failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwpost1
ORA-27303: additional information: semid = 786434
ORA-00600: internal error code, arguments: [2662], [1], [451386467], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [1], [451386466], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Sat Apr 11 20:59:56 2026
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_31992.trc (incident=139601):
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [2662], [1], [451386467], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [1], [451386466], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_139601/orcl11g_ora_31992_i139601.trc
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_139601/orcl11g_ora_31992_i139601.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [2662], [1], [451386467], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [1], [451386466], [1], [451414602], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [1], [451386464], [1], [451414602], [12583040], [], [], [], [], [], []第二次重启
Sat Apr 11 21:06:25 2026
SMON: enabling cache recovery
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_161360.trc (incident=139761):
ORA-00600: internal error code, arguments: [2663], [1], [451406472], [1], [451414602], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_139761/orcl11g_ora_161360_i139761.trc
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_161360.trc:
ORA-00600: internal error code, arguments: [2663], [1], [451406472], [1], [451414602], [], [], [], [], [], [], []
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_161360.trc:
ORA-00600: internal error code, arguments: [2663], [1], [451406472], [1], [451414602], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER (ospid: 161360): terminating the instance due to error 600第三次重启出现
ORA-00600: internal error code, arguments: [4137], [18.28.1260154], [0], [0], [], [], [], [], [], [], [], []
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_smon_54813.trc (incident=143713):
ORA-00600: internal error code, arguments: [4137], [18.28.1260154], [0], [0], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_143713/orcl11g_smon_54813_i143713.trc
Database Characterset is ZHS16GBK
No Resource Manager plan active
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_56562.trc (incident=143761):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_143761/orcl11g_ora_56562_i143761.trc
ORACLE Instance orcl11g (pid = 13) - Error 600 encountered while recovering transaction (18, 28).
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_smon_54813.trc:
ORA-00600: internal error code, arguments: [4137], [18.28.1260154], [0], [0], [], [], [], [], [], [], [], []
Sat Apr 11 21:07:57 2026之后多次重启均出现ORA-00600: [4193]
redo当前状态下进行不完全恢复主库后resetlogs 报错继续报错ORA-00600: internal error code, arguments: [4193], [227], [240]，
修改参数文件，增加如下参数
undo_management = manual
event = '10513 trace name context forever, level 2'
_corrupted_rollback_segments=(_SYSSMU18_1772509237$)
ORA-00600: internal error code, arguments: [4194], [18.28.1260154], [0], [], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_143714/orcl11g_smon_54813_i143714.trc
Trace dumping is performing id=[cdmp_20260411210758]
replication_dependency_tracking turned off (no async multimaster replication found)
Doing block recovery for file 3 block 1178
Resuming block recovery (PMON) for file 3 block 1178
Block recovery from logseq 3, block 100 to scn 4746393864
Recovery of Online Redo Log: Thread 1 Group 3 Seq 3 Reading mem 0
Mem# 0: /opt/app/oracle/product/oradata/orcl11g/redo03.log
Block recovery stopped at EOT rba 3.105.16
Block recovery completed at rba 3.105.16, scn 1.451426565
Doing block recovery for file 3 block 208
Resuming block recovery (PMON) for file 3 block 208
Block recovery from logseq 3, block 100 to scn 4746393860
Recovery of Online Redo Log: Thread 1 Group 3 Seq 3 Reading mem 0
Mem# 0: /opt/app/oracle/product/oradata/orcl11g/redo03.log
Block recovery completed at rba 3.105.16, scn 1.451426565
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_smon_54813.trc:
ORA-01595: error freeing extent (3) of rollback segment (6))
ORA-00600: internal error code, arguments: [4194], [18.28.1260154], [3], [], [], [], [], [], [], [], [], []
Sat Apr 11 21:07:59 2026
Trace dumping is performing id=[cdmp_20260411210759]
Starting background process QMNC
Sat Apr 11 21:07:59 2026
QMNC started with pid=25, OS id=58589
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3DC87A04] [PC:0x2283E8C, kgegpa()+40] [flags: 0x0, count: 1]
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3DC87A04] [PC:0x22820B7, kgebse()+279] [flags: 0x2, count: 2]
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3DC87A04] [PC:0x22820B7, kgebse()+279] [flags: 0x2, count: 2]
Sat Apr 11 21:08:01 2026
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_mmon_54842.trc (incident=143729):
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_143729/orcl11g_mmon_54842_i143729.trc
Trace dumping is performing id=[cdmp_20260411210803]
Doing block recovery for file 3 block 1937
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_pmon_54646.trc (incident=143625):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_143625/orcl11g_pmon_54646_i143625.trc
Sat Apr 11 21:08:18 2026
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_60248.trc (incident=147616):
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_147616/orcl11g_ora_60248_i147616.trc
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_147616/orcl11g_ora_60248_i147616.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Trace dumping is performing id=[cdmp_20260411210818]
Sat Apr 11 21:08:19 2026
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_60319.trc (incident=147624):
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_147624/orcl11g_ora_60319_i147624.trc
Errors in file /opt/app/oracle/product/diag/rdbms/orcl11g/orcl11g/incident/incdir_147624/orcl11g_ora_60319_i147624.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Doing block recovery for file 3 block 1840oracle官方文档处理方案，由此可见是在多次resetlogs重启之后出现了UNDO
oracle support 文档 1428786.1
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=cld99whp9_53&_afrLoop=278414555589218#SYMPTOM
引起的原因
收缩后可能会导致撤消损坏。相同的撤消块可能用于两个不同的事务，从而导致多个内部错误，例如：
ORA-600 [4193] / ORA-600 [4194]用于新事务
ORA-600 [4137]用于事务回滚
官方的解决文档步骤如下：
Best practice to create a new undo tablespace.
This method includes segment check.
1. Create pfile from spfile to edit
SQL> Create pfile='/tmp/initsid.ora' from spfile;
2. Shutdown the instance
3. set the following parameters in the pfile /tmp/initsid.ora
undo_management = manual
event = '10513 trace name context forever, level 2'
4. SQL>>startup restrict pfile='/tmp/initsid.ora'
5. SQL>select tablespace_name, status, segment_name from dba_rollback_segs where status != 'OFFLINE';
This is critical - we are looking for all undo segments to be offline - System will always be online.
If any are 'PARTLY AVAILABLE' or 'NEEDS RECOVERY' - Please open an issue with Oracle Support or update the current SR. There are many options from this moment and Oracle Support Analyst can offer different solutions for the bad undo segments.
If all offline then continue to the next step
6. Create new undo tablespace - example
SQL>create undo tablespace <new undo tablespace> datafile <datafile> size 2000M;
7. Drop old undo tablespace
SQL>drop tablespace <old undo tablespace> including contents and datafiles;
8. SQL>shutdown immediate;
9 SQL>startup nomount; --> Using your Original spfile
10. Modify the spfile with the new undo tablespace name
SQL> Alter system set undo_tablespace = '<new tablespace created in step 6>' scope=spfile;
11. SQL>shutdown immediate;
12. SQL>startup; --> Using spfile按照以上方式处理之后数据库恢复成功。
其他问题
在按照以上方式处理的过程中，删除旧的UNDO表空间的时候出现无法删除的情况，提示有一个回滚段在使用中。
ORA-01548: active rollback segment '_SYSSMU18_1772509237$' found, terminate
dropping tablespace
经过查询：
这属于 _allow_resetlogs_corruption 强制恢复后的典型后遗症，核心思路是先欺骗数据库跳过对这些损坏回滚段的检查，删除表空间，最后再把参数改回来。
SQL> select tablespace_name, status, segment_name from dba_rollback_segs where status != 'OFFLINE';
TABLESPACE_NAME STATUS SEGMENT_NAME
------------------------------ ---------------- ------------------------------
SYSTEM ONLINE SYSTEM
UNDOTBS1 PARTLY AVAILABLE _SYSSMU18_1772509237$处理方法如下：
第一步：切换到"手动"模式并屏蔽损坏段
SQL> CREATE PFILE='/tmp/init.ora.bak' FROM SPFILE;
修改参数文件：
# 注释掉原来的 undo 相关参数（加 # 号或直接删除原行）
# undo_management=AUTO
# undo_tablespace=UNDOTBS1
# 添加以下两行，改为手动模式并屏蔽报错的回滚段
undo_management = manual
event = '10513 trace name context forever, level 2'
_corrupted_rollback_segments=(_SYSSMU18_1772509237$)注意：如果报错信息中还有其他 _SYSSMU... 段，请用逗号分隔，全部填进去。
使用新 PFILE 重启数据库：
SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MOUNT PFILE='/path/to/your/init.ora';
SQL> ALTER DATABASE OPEN;
第二步：执行强制删除
数据库现在已经忽略了指定的损坏回滚段，可以执行删除了。
SQL> DROP TABLESPACE undotbs1 INCLUDING CONTENTS AND DATAFILES;