ORACLE无法连接，报ORA-445错误，请高手帮忙分析，谢谢！

2013-10-24 12:18:35 1.8k 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

Oracle连接满了，无法登录数据库，如何分析连接来源？本文将介绍如何分析连接来源，并提供排查思路和解决方案，帮助 DBA 快速恢复数据库的正常运行。，问题可能会再次发生。因此，我们需要分析连接来源并采取针对性措施。可以重启应用或重启数据库来释放连接，但如果不找到。，并采取适当的优化措施，保障数据库稳定运行。在日常数据库运维中，我们可能会遇到。找到对应的 Java 应用。通过这些方法，可以有效排查。在生产环境中，我们收到了。，新连接请求无法被受理。在数据库服务器上，使用。阅读详情

*** 2013-10-01 15:19:40.508
Process diagnostic dump for M000, OS id=11452
-------------------------------------------------------------------------------
Memory (Avail/Total): Ph:4317M/16371M, Ph+PgF:20444M/32740M

Stack:
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
------------------------------------------- ------------------------------------------- ---------------- ---------------- ---------------- ----------------
0000000076D7F6FA 0000000000000000 0000000000000000 000000000994dc0f 000000001ad29ef0 00000083051ef396
000007FEFCF710AC 0000000076D7F6F0 000000002fc1f848 0000000000000042 000000002fc1fc40 0000000027e2d640
sskgmfindrealm()+37 000007FEFCF71010 000000002fc1fb30 0000000000000000 0005000200000000 00000000000001a8
skgmattach()+261 sskgmfindrealm() 0000000000032000 0000000000159000 ffffffffffffffff ffffffffffffffff
ksmlsge_phaseone()+395 skgmattach()+253 000000000d6800df 0000000000000000 000000000d680088 0000000000000049
opimai_init()+151 ksmlsge_phaseone() 0000000000000000 0000000000000000 0000000000000000 0000000000000000
opimai_real()+247 opimai_init() 01cebe7673b070ef 0000000000000000 000f0001000a07dd 0002029c00270012
opimai()+191 opimai_real() 0000000000000000 0000000000000000 0000000000000000 0000000000000000
BackgroundThreadStart()+693 opimai() 000000002fc1fe58 0000000000000001 0000000000000000 0000000000000000
0000000076C2F33D BackgroundThreadStart() 000000004e1905d0 0000000000000000 0000000000000000 0000000000000000
0000000076D62CA1 0000000076C2F330 0000000000000000 0000000000000000 0000000000000000 0000000000000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 141 ms
symbol translation time: 93 ms
total time: 234 ms

-------------------------------------------------------------------------------
Process diagnostic dump actual duration=0.343000 sec
(max dump time=30.000000 sec)

*** 2013-10-01 15:19:40.851

*** 2013-10-01 15:19:56.061
Waited for process M000 to initialize for 76 seconds

...全文

记一次ORA600内部错误故障分析与修复实录 202X年X月X日，某用户的Oracle数据库在上午9点至10点期间发生故障，导致部分业务无法正常运行。经初步分析，发现数据库报出 `ORA-00600` 内部错误。该错误是Oracle的一个通用错误，通常由数据库内部逻辑异常、数据块损坏或存储问题引起。阅读详情

sysadm_cc

Oracle 高级技术 3,499 成员 18,710 内容

+ 关注 + 加入社区

切换为时间正序

居然有人说长得比我帅 2013-10-31

打赏
举报

这个跟你好像 http://t.askmaclean.com/thread-1093-1-1.html

sysadm_cc 2013-10-31

打赏
举报

引用 3 楼 comerliang 的回复:

在服务器上用sqlplus也连不上？

是的

Comer 2013-10-30

打赏
举报

在服务器上用sqlplus也连不上？

sysadm_cc 2013-10-24

打赏
举报

Trace file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_mmon_2276.trc Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Windows NT Version V6.1 CPU : 4 - type 8664, 4 Physical Cores Process Affinity : 0x0x0000000000000000 Memory (Avail/Total): Ph:4024M/16371M, Ph+PgF:20073M/32740M Instance name: orcl Redo thread mounted by this instance: 1 Oracle process number: 15 Windows thread id: 2276, image: ORACLE.EXE (MMON) *** 2013-09-13 17:45:24.007 *** SESSION ID:(190.1) 2013-09-13 17:45:24.007 *** CLIENT ID:() 2013-09-13 17:45:24.007 *** SERVICE NAME:(SYS$BACKGROUND) 2013-09-13 17:45:24.007 *** MODULE NAME:() 2013-09-13 17:45:24.007 *** ACTION NAME:() 2013-09-13 17:45:24.007 *** TRACE FILE RECREATED AFTER BEING REMOVED *** ORA-00020: No more process state objects available *** 2013-09-13 17:45:24.194 kraalac: unable to schedule MMON slave, error 3 ORA-00020: No more process state objects available *** 2013-09-13 18:33:36.081 ktte_monitor_ts: unable to schedule MMON Slave, error 3 ORA-00020: No more process state objects available ***ket_aba_spawn: unable to schedule MMON Slave, error 3 AUTO MEM: pga_aggregate_target resize. manual=0, toggle=0 AUTO MEM: pga_aggregate_target resize. manual=0, toggle=0 Waited for process M000 to initialize for 60 seconds *** 2013-10-01 15:19:40.508 Process diagnostic dump for M000, OS id=11452 ------------------------------------------------------------------------------- Memory (Avail/Total): Ph:4317M/16371M, Ph+PgF:20444M/32740M Stack: ------------------- Call Stack Trace --------------------- calling location entry point arg #1 arg #2 arg #3 arg #4 ------------------------------------------- ------------------------------------------- ---------------- ---------------- ---------------- ---------------- 0000000076D7F6FA 0000000000000000 0000000000000000 000000000994dc0f 000000001ad29ef0 00000083051ef396 000007FEFCF710AC 0000000076D7F6F0 000000002fc1f848 0000000000000042 000000002fc1fc40 0000000027e2d640 sskgmfindrealm()+37 000007FEFCF71010 000000002fc1fb30 0000000000000000 0005000200000000 00000000000001a8 skgmattach()+261 sskgmfindrealm() 0000000000032000 0000000000159000 ffffffffffffffff ffffffffffffffff ksmlsge_phaseone()+395 skgmattach()+253 000000000d6800df 0000000000000000 000000000d680088 0000000000000049 opimai_init()+151 ksmlsge_phaseone() 0000000000000000 0000000000000000 0000000000000000 0000000000000000 opimai_real()+247 opimai_init() 01cebe7673b070ef 0000000000000000 000f0001000a07dd 0002029c00270012 opimai()+191 opimai_real() 0000000000000000 0000000000000000 0000000000000000 0000000000000000 BackgroundThreadStart()+693 opimai() 000000002fc1fe58 0000000000000001 0000000000000000 0000000000000000 0000000076C2F33D BackgroundThreadStart() 000000004e1905d0 0000000000000000 0000000000000000 0000000000000000 0000000076D62CA1 0000000076C2F330 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ---------------- End of Call Stack Trace ----------------- Call stack acquisition performance stats: setup time (lock acquis., memory alloc.): 0 ms frame get time (time the target proc was suspended): 141 ms symbol translation time: 93 ms total time: 234 ms ------------------------------------------------------------------------------- Process diagnostic dump actual duration=0.343000 sec (max dump time=30.000000 sec) *** 2013-10-01 15:19:40.851 *** 2013-10-01 15:19:56.061 Waited for process M000 to initialize for 76 seconds

sysadm_cc 2013-10-24

打赏
举报

log.xml文件内容： <msg time='2013-10-01T15:20:45.591+08:00' org_id='oracle' comp_id='rdbms' msg_id='4233499900' type='INCIDENT_ERROR' level='1' host_id='RAYDA-DB' host_addr='fe80::820:2840:3f53:9014%13' prob_key='ORA 445' upstream_comp='' downstream_comp='background_proc' ecid='' errid='21721' detail_path='d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_mmon_2276.trc'> <txt>Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_mmon_2276.trc (incident=21721): ORA-00445: background process "m000" did not start after 120 seconds

ORACLE无法连接，报ORA-445错误，请高手帮忙分析，谢谢！

相关推荐