标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2131 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (102)
- 数据库 (1,671)
- DB2 (22)
- MySQL (73)
- Oracle (1,533)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (21)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (14)
- ORACLE 21C (3)
- Oracle 23ai (7)
- Oracle ASM (65)
- Oracle Bug (8)
- Oracle RAC (52)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (560)
- Oracle安装升级 (92)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (78)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- Kylin Linux 安装19c
- ORA-600 krse_arc_complete.4
- Oracle 19c 202410补丁(RUs+OJVM)
- ntfs MFT损坏(ntfs文件系统故障)导致oracle异常恢复
- .mkp扩展名oracle数据文件加密恢复
- 清空redo,导致ORA-27048: skgfifi: file header information is invalid
- A_H_README_TO_RECOVER勒索恢复
- 通过alert日志分析客户自行对一个数据库恢复的来龙去脉和点评
- ORA-12514: TNS: 监听进程不能解析在连接描述符中给出的SERVICE_NAME
- ORA-01092 ORA-00604 ORA-01558故障处理
- ORA-65088: database open should be retried
- Oracle 19c异常恢复—ORA-01209/ORA-65088
- ORA-600 16703故障再现
- 数据库启动报ORA-27102 OSD-00026 O/S-Error: (OS 1455)
- .[metro777@cock.li].Elbie勒索病毒加密数据库恢复
- 应用连接错误,初始化mysql数据库恢复
- RAC默认服务配置优先节点
- Oracle 19c RAC 替换私网操作
- 监听报TNS-12541 TNS-12560 TNS-00511错误
- drop tablespace xxx including contents恢复
2662 的搜索结果
硬件故障导致ORA-600 2662错误处理
前几天恢复了一个40多T的CASE:ORA-00600: internal error code, arguments: [16513], [1403] 恢复,又一个近30T的库由于硬件故障,通过其他人一系列恢复之后,无法正常open,让我们提供技术支持:
故障最初原因是由于存储异常
Fri Feb 19 09:03:49 2021 Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_ora_3460.trc: ORA-01114: 将块写入文件 849 时出现 IO 错误 (块 # 3871748) ORA-27070: 异步读取/写入失败 OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 1167) 设备没有连接。 ORA-01114: 将块写入文件 849 时出现 IO 错误 (块 # 3871748) ORA-27070: 异步读取/写入失败 OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 1167) 设备没有连接。
通过其他人一系列处理后,数据库报ORA-600 2662错误
Sat Feb 20 08:19:35 2021 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sat Feb 20 08:19:35 2021 SMON: enabling cache recovery Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_ora_5304.trc(incident=1960181): ORA-00600:internal error code,arguments:[2662],[4],[2185364344], [4],[2185453722],[893388032],[],[],[],[],[],[] Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_ora_5304.trc: ORA-00600:internal error code,arguments:[2662],[4],[2185364344], [4],[2185453722],[893388032],[],[],[],[],[],[] Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_ora_5304.trc: ORA-00600:internal error code,arguments:[2662],[4],[2185364344], [4],[2185453722],[893388032],[],[],[],[],[],[] Error 600 happened during db open, shutting down database USER (ospid: 5304): terminating the instance due to error 600 Instance terminated by USER, pid = 5304 ORA-1092 signalled during: ALTER DATABASE OPEN... opiodr aborting process unknown ospid (5304) as a result of ORA-1092 Sat Feb 20 08:19:42 2021 ORA-1092 : opitsk aborting process
通过对scn处理,数据库顺利绕过该错误,然后报ORA-600 4194错误
Doing block recovery for file 213 block 4688 No block recovery was needed Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_smon_7048.trc(incident=1984136): ORA-00600: internal error code, arguments: [4194], [38.4.1381252], [0], [], [],[],[],[],[],[],[],[] Sat Feb 20 10:50:45 2021 Doing block recovery for file 213 block 4688 No block recovery was needed Fatal internal error happened while SMON was doing active transaction recovery. Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_smon_7048.trc: ORA-00600: internal error code, arguments: [4194], [38.4.1381252], [0], [], [],[],[],[],[],[],[],[] SMON (ospid: 7048): terminating the instance due to error 474 Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_ora_6652.trc(incident=1984185): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] Sat Feb 20 10:50:52 2021 Instance terminated by SMON, pid = 7048
通过对异常事务进行处理,屏蔽smon进程进行回滚,数据库open成功,但是报ORA-600 4137错误
Sat Feb 20 10:53:46 2021 Sweep [inc][1992133]: completed Stopping background process MMNL Sat Feb 20 10:53:47 2021 Trace dumping is performing id=[cdmp_20210220105347] Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_smon_6576.trc(incident=1992134): ORA-00600: internal error code, arguments: [4137], [23.13.3094188], [0], [0], [], [], [], [], [], [], [], [] ORACLE Instance xifenfei (pid = 14) - Error 600 encountered while recovering transaction (23, 13). Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_smon_6576.trc: ORA-00600: internal error code, arguments: [4137], [23.13.3094188], [0], [0], [], [], [], [], [], [], [], [] Sat Feb 20 10:53:47 2021 Sweep [inc2][1992133]: completed Sat Feb 20 10:53:47 2021 Sweep [inc][1992134]: completed Stopping background process MMON Trace dumping is performing id=[cdmp_20210220105348] Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_smon_6576.trc(incident=1992135): ORA-00600: internal error code, arguments: [4137], [38.4.1381252], [0], [0], [], [], [], [], [], [], [], [] Starting background process MMON Starting background process MMNL Sat Feb 20 10:53:48 2021 MMON started with pid=16, OS id=6448 ALTER SYSTEM enable restricted session; Sat Feb 20 10:53:48 2021 MMNL started with pid=36, OS id=6840 ORACLE Instance xifenfei (pid = 14) - Error 600 encountered while recovering transaction (38, 4). Errors in file d:\app\administrator\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_smon_6576.trc: ORA-00600: internal error code, arguments: [4137], [38.4.1381252], [0], [0], [], [], [], [], [], [], [], [] Sat Feb 20 10:53:49 2021 Sweep [inc][1992135]: completed Trace dumping is performing id=[cdmp_20210220105349] replication_dependency_tracking turned off (no async multimaster replication found) Completed: alter database open
对异常回滚段进行处理,数据库后端启动正常,不再报明显ORA-错误.通过hcheck.sql检查字典正常
HCheck Version 07MAY18 on 20-FEB-2021 11:35:11 ---------------------------------------------- Catalog Version 11.2.0.1.0 (1102000100) db_name: JYJG Catalog Fixed Procedure Name Version Vs Release Timestamp Result ------------------------------ ... ---------- -- ---------- -------------- ------ .- LobNotInObj ... 1102000100 <= *All Rel* 02/20 11:35:11 PASS .- MissingOIDOnObjCol ... 1102000100 <= *All Rel* 02/20 11:35:11 PASS .- SourceNotInObj ... 1102000100 <= *All Rel* 02/20 11:35:11 PASS .- IndIndparMismatch ... 1102000100 <= 1102000100 02/20 11:35:12 PASS .- InvCorrAudit ... 1102000100 <= 1102000100 02/20 11:35:12 PASS .- OversizedFiles ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- PoorDefaultStorage ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- PoorStorage ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- PartSubPartMismatch ... 1102000100 <= 1102000100 02/20 11:35:12 PASS .- TabPartCountMismatch ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- OrphanedTabComPart ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- MissingSum$ ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- MissingDir$ ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- DuplicateDataobj ... 1102000100 <= *All Rel* 02/20 11:35:12 PASS .- ObjSynMissing ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- ObjSeqMissing ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedUndo ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedIndex ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedIndexPartition ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedIndexSubPartition ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedTable ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedTablePartition ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedTableSubPartition ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- MissingPartCol ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedSeg$ ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- OrphanedIndPartObj# ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- DuplicateBlockUse ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- FetUet ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- Uet0Check ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- ExtentlessSeg ... 1102000100 <= 1102000100 02/20 11:35:13 PASS .- SeglessUET ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- BadInd$ ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- BadTab$ ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- BadIcolDepCnt ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- ObjIndDobj ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- TrgAfterUpgrade ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- ObjType0 ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- BadOwner ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- StmtAuditOnCommit ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- BadPublicObjects ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- BadSegFreelist ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- BadDepends ... 1102000100 <= *All Rel* 02/20 11:35:13 PASS .- CheckDual ... 1102000100 <= *All Rel* 02/20 11:35:14 PASS .- ObjectNames ... 1102000100 <= *All Rel* 02/20 11:35:14 PASS .- BadCboHiLo ... 1102000100 <= *All Rel* 02/20 11:35:14 PASS .- ChkIotTs ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- NoSegmentIndex ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- BadNextObject ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- DroppedROTS ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- FilBlkZero ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- DbmsSchemaCopy ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- OrphanedObjError ... 1102000100 > 1102000000 02/20 11:35:15 PASS .- ObjNotLob ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- MaxControlfSeq ... 1102000100 <= *All Rel* 02/20 11:35:15 PASS .- SegNotInDeferredStg ... 1102000100 > 1102000000 02/20 11:35:18 PASS .- SystemNotRfile1 ... 1102000100 > 902000000 02/20 11:35:18 PASS .- DictOwnNonDefaultSYSTEM ... 1102000100 <= *All Rel* 02/20 11:35:19 PASS .- OrphanTrigger ... 1102000100 <= *All Rel* 02/20 11:35:19 PASS .- ObjNotTrigger ... 1102000100 <= *All Rel* 02/20 11:35:19 PASS --------------------------------------- 20-FEB-2021 11:35:19 Elapsed: 8 secs --------------------------------------- Found 0 potential problem(s) and 0 warning(s) PL/SQL procedure successfully completed. Statement processed.
虽然字典正常,但是由于数据库屏蔽了一致性,建议客户在条件允许的情况下,进行逻辑迁移,排除风险隐患.
发表在 非常规恢复
标签为 O/S-Error: (OS 1167), ORA-01114, ORA-27070, ORA-600 2662, ORA-600 4137, ORA-600 4194, OSD-04016
评论关闭
ORA-00600 [2662]和ORA-00600 [4194]恢复
Sat Dec 26 19:34:05 2020 alter database open Beginning crash recovery of 1 threads parallel recovery started with 7 processes Started redo scan Completed redo scan read 0 KB redo, 0 data blocks need recovery Started redo application at Thread 1: logseq 24, block 2, scn 2621149392 Recovery of Online Redo Log: Thread 1 Group 3 Seq 24 Reading mem 0 Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG Completed redo application of 0.00MB Completed crash recovery at Thread 1: logseq 24, block 3, scn 2621169394 0 data blocks read, 0 data blocks written, 0 redo k-bytes read Sat Dec 26 19:34:06 2020 Thread 1 advanced to log sequence 25 (thread open) Thread 1 opened at log sequence 25 Current log# 1 seq# 25 mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO01.LOG Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sat Dec 26 19:34:06 2020 SMON: enabling cache recovery Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc (incident=110636): ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], [] Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc: ORA-00704: 引导程序进程失败 ORA-00704: 引导程序进程失败 ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], [] Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc: ORA-00704: 引导程序进程失败 ORA-00704: 引导程序进程失败 ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], [] Error 704 happened during db open, shutting down database USER (ospid: 5812): terminating the instance due to error 704 Instance terminated by USER, pid = 5812 ORA-1092 signalled during: alter database open... opiodr aborting process unknown ospid (5812) as a result of ORA-1092 Sat Dec 26 19:34:10 2020 ORA-1092 : opitsk aborting process
对应的trace文件内容,主要在查询undo$表触发ORA-600 2662错误
通过修改scn,解决ORA-600 2662错误之后,数据库启动报ORA-600 4194
Sat Dec 26 20:13:28 2020 SMON: enabling tx recovery Database Characterset is ZHS16GBK Trace dumping is performing id=[cdmp_20201226201328] No Resource Manager plan active Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_smon_8104.trc (incident=114188): ORA-00600: internal error code, arguments: [4194], [], [ Incident details in: e:\oracle\app\administrator\diag\rdbms\xff\xff\incident\incdir_114188\xff_smon_8104_i114188.trc Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x470E9BAC] [PC:0x6F21343, ___dyn_tls_init_callback()+111576860] Sat Dec 26 20:13:29 2020 Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\cdump\xffcore.log ORA-07445: caught exception [ACCESS_VIOLATION] at [___dyn_tls_init_callback()+111576860] [0x06F21343] Doing block recovery for file 3 block 3121 Resuming block recovery (PMON) for file 3 block 3121 Block recovery from logseq 12, block 73 to scn 3221225727 Recovery of Online Redo Log: Thread 1 Group 3 Seq 12 Reading mem 0 Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG Block recovery stopped at EOT rba 12.75.16 Block recovery completed at rba 12.75.16, scn 0.3221225724 Doing block recovery for file 3 block 176 Resuming block recovery (PMON) for file 3 block 176 Block recovery from logseq 12, block 73 to scn 3221225721 Recovery of Online Redo Log: Thread 1 Group 3 Seq 12 Reading mem 0 Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG Block recovery completed at rba 12.73.16, scn 0.3221225722 Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_smon_8104.trc: ORA-01595: error freeing extent (3) of rollback segment (4)) ORA-00600: internal error code, arguments: [4194], [], [ Trace dumping is performing id=[cdmp_20201226201331] Sat Dec 26 20:13:31 2020 PMON (ospid: 5200): terminating the instance due to error 397 Instance terminated by PMON, pid = 5200
解决异常undo,数据库启动正常,导出数据
正常open库报ORA-600 2662,ORA-600 4097错误
又一起数据库正常open之后继续报ORA-600 2662
Sat Dec 29 04:30:40 2018 QMNC started with pid=36, OS id=12985 LOGSTDBY: Validating controlfile with logical metadata LOGSTDBY: Validation complete Completed: alter database open Sat Dec 29 04:30:42 2018 Starting background process CJQ0 Sat Dec 29 04:30:42 2018 CJQ0 started with pid=41, OS id=12999 Sat Dec 29 04:30:43 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_m000_12989.trc (incident=365101): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Sat Dec 29 04:30:43 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_m002_12993.trc (incident=365117): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365101/orcl_m000_12989_i365101.trc Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365117/orcl_m002_12993_i365117.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_m000_12989.trc (incident=365102): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365102/orcl_m000_12989_i365102.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_m002_12993.trc (incident=365118): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365118/orcl_m002_12993_i365118.trc
在open状态处理掉ORA-00600 2662错误之后,又出现了ORA-600 4097 以及ORA-00353 ORA-00312错误,这个也是一种不常见的现象,一般都是数据库open之前出现类似错误,但是这里在open之后出现(以前类似处理参考:ORA-600 4097故障处理和ORA-00322 ORA-00312 ,ORA-00354 ORA-00353 ORA-00312异常处理)
Sat Dec 29 05:55:22 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j000_19136.trc (incident=432567): ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432567/orcl_j000_19136_i432567.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j000_19136.trc (incident=432568): ORA-00353: log corruption near block 15682 change 193647101 time 12/29/2018 04:40:31 ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432568/orcl_j000_19136_i432568.trc Errors in file /home/app/diag/rdbms/orcl/orcl/incident/incdir_432567/orcl_j000_19136_i432567.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 15682 change 193647101 time 12/29/2018 04:40:31 ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j000_19136.trc (incident=432569): ORA-00353: log corruption near block 15682 change 193647101 time 12/29/2018 04:40:31 ORA-00334: archived log: '/home/app/oradata/orcl/redo03.log' ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432569/orcl_j000_19136_i432569.trc
处理完成上面报错之后,继续出现比较少见的ORA-600 ktecgsc:kcbz_objdchk错误,具体参考:ORA-00600 [ktecgsc:kcbz_objdchk] on 11.2 (Doc ID 1562473.1)
Sat Dec 29 06:00:17 2018 DBMS_STATS: GATHER_STATS_JOB encountered errors. Check the trace file. Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j001_19436.trc: ORA-20011: Approximate NDV failed: ORA-08103: object no longer exists Sat Dec 29 06:00:21 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j002_19479.trc (incident=432631): ORA-00600: internal error code, arguments: [ktecgsc:kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432631/orcl_j002_19479_i432631.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details.