各位大佬请问下 数据库启动报这个错怎么处理ORA-03113: end-of-file on communication channel？
各位大佬请问下
SQL> startup
ORACLE instance started.
Total System Global Area 2.9262E+10 bytes
Fixed Size 2242504 bytes
Variable Size 3556771896 bytes
Database Buffers 2.5636E+10 bytes
Redo Buffers 67850240 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 7631
Session ID: 937 Serial number: 3
error 472 detected in background process
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
kjzduptcctx: Notifying DIAG for crash event
----- Abridged Call Stack Trace -----
ksedsts()+461<-kjzdssdmp()+267<-kjzduptcctx()+232<-kjzdicrshnfy()+53<-ksuitm()+1332<-ksbrdp()+3344<-opirip()+623<-opidrv()+603<-sou2o()+103<-opimai_real()+266<-ssthrdmain()+252<-main()+201<-__libc_start_main()+253<-_start()+36
----- End of Abridged Call Stack Trace -----
* 2017-09-05 18:48:36.249
PMON (ospid: 7576): terminating the instance due to error 472
ksuitm: waiting up to [5] seconds before killing DIAG(7586)
数据库启动报这个错怎么处理?
alert里边看到是redo恢复的时候出了错。。
Recovery of Online Redo Log: Thread 1 Group 5 Seq 47 Reading mem 0
Mem# 0: /data1/oracle/app/oradata/njhb/redo05.log
Block recovery completed at rba 47.204.16, scn 0.33145327
Block recovery from logseq 47, block 202 to scn 33145446
Recovery of Online Redo Log: Thread 1 Group 5 Seq 47 Reading mem 0
Mem# 0: /data1/oracle/app/oradata/njhb/redo05.log
Block recovery completed at rba 47.290.16, scn 0.33145447
Block recovery from logseq 47, block 202 to scn 33145324
Recovery of Online Redo Log: Thread 1 Group 5 Seq 47 Reading mem 0
Mem# 0: /data1/oracle/app/oradata/njhb/redo05.log
Block recovery completed at rba 47.204.16, scn 0.33145327
Block recovery from logseq 47, block 202 to scn 33145448
Recovery of Online Redo Log: Thread 1 Group 5 Seq 47 Reading mem 0
Mem# 0: /data1/oracle/app/oradata/njhb/redo05.log
Block recovery completed at rba 47.292.16, scn 0.33145449
Tue Sep 05 18:44:02 2017
Block recovery from logseq 47, block 202 to scn 33145324
Recovery of Online Redo Log: Thread 1 Group 5 Seq 47 Reading mem 0
Mem# 0: /data1/oracle/app/oradata/njhb/redo05.log
Block recovery completed at rba 47.204.16, scn 0.33145327
Block recovery from logseq 47, block 202 to scn 33145450
Recovery of Online Redo Log: Thread 1 Group 5 Seq 47 Reading mem 0
Mem# 0: /data1/oracle/app/oradata/njhb/redo05.log
Block recovery completed at rba 47.298.16, scn 0.33145451
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 36 out of maximum 100 non-fatal internal errors.
3同行回答
ORA-00600: internal error code, arguments: [4194], [45], [44], [], [], [], [], []
4194错误通常说明UNDO段出现问题,最好的办法是通过备份进行恢复,如果没有备份,那么可以通过特殊的初始化参数进行强制启动,本文就Oracle的隐含参数进行恢复说明(由于实际情况可能各不相同，进行测试前请先行备份)，仅供参考。
去确定当前回滚段名称，这可以从alert文件中获得
- 请问是否是生产数据库，可参考如下资料，情况如何，写下结帖。数据库问题是大事儿。 http://www.eygle.com/archives/2006/02/howto_resolve_ora_600_4194.html
- alert里边看到是redo恢复的时候出了错。。Non-fatal internal error happenned while SMON was doing logging scn->time mapping. SMON encountered 36 out of maximum 100 non-fatal internal errors. 文档里边说的undo的问题呢。
- 嗯嗯，具体问题具体分析，发发alter.log
- Errors in file /data1/oracle/app/diag/rdbms/orcl/orcl/trace/orcl_mmon_9137.trc (incident=204261): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Block recovery from logseq 51, block 90 to scn 33227010 Recovery of Online Redo Log: Thread 1 Group 3 Seq 51 Reading mem 0 Mem# 0: /data1/oracle/app/oradata/njhb/redo03.log Block recovery completed at rba 51.92.16, scn 0.33227012 Block recovery from logseq 51, block 90 to scn 33227015 Recovery of Online Redo Log: Thread 1 Group 3 Seq 51 Reading mem 0 Mem# 0: /data1/oracle/app/oradata/njhb/redo03.log Block recovery completed at rba 51.96.16, scn 0.33227016 Errors in file /data1/oracle/app/diag/rdbms/orcl/orcl/trace/orcl_mmon_9137.trc (incident=204262): ORA-00600: internal error code, arguments: [kewrose_1], [600], [ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] ], [], [], [], [], [], [], [], [], [] Incident details in: /data1/oracle/app/diag/rdbms/orcl/orcl/incident/incdir_204262/orcl_mmon_9137_i204262.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3D0EADE6] [PC:0x932F8EA, kgegpa()+40] [flags: 0x0, count: 1] Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3D0EADE6] [PC:0x932DEF3, kgebse()+771] [flags: 0x2, count: 2] Tue Sep 05 21:02:23 2017 Dumping diagnostic data in directory=[cdmp_20170905210223], requested by (instance=1, osid=9137 (MMON)), summary=[incident=204262]. Block recovery from logseq 51, block 90 to scn 33227010 Recovery of Online Redo Log: Thread 1 Group 3 Seq 51 Reading mem 0 Mem# 0: /data1/oracle/app/oradata/njhb/redo03.log Block recovery completed at rba 51.92.16, scn 0.33227012 Errors in file /data1/oracle/app/diag/rdbms/orcl/orcl/trace/orcl_pmon_8946.trc (incident=192276): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] 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 /data1/oracle/app/diag/rdbms/orcl/orcl/trace/orcl_pmon_8946.trc: ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] PMON (ospid: 8946): terminating the instance due to error 472 System state dump requested by (instance=1, osid=8946 (PMON)), summary=[abnormal instance termination]. System State dumped to trace file /data1/oracle/app/diag/rdbms/orcl/orcl/trace/orcl_diag_8956.trc Dumping diagnostic data in directory=[cdmp_20170905210224], requested by (instance=1, osid=8946 (PMON)), summary=[abnormal instance termination]. Instance terminated by PMON, pid = 8946