반응형
| "Pmon Failed To Acquire Latch" Messages in Alert Log -Database Hung [ID 468740.1] | |||||
| 수정 날짜 15-SEP-2010 유형 PROBLEM 상태 MODERATED | |||||
In this Document
Symptoms
Cause
Solution
References
Platforms: 1-914CU;
| This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.7 - Release: 10.2 to 11.1Information in this document applies to any platform.
***Checked for relevance on 15-Sep-2010***
Symptoms
Database Instance hangs and connections to database using 'sqlplus' are also not possible.Checking alert.log we see following messages
PMON failed to acquire latch, see PMON dump
Fri Oct 5 10:33:00 2007
PMON failed to acquire latch, see PMON dump
Fri Oct 5 10:34:05 2007
PMON failed to acquire latch, see PMON dump
Errors in file /dwrac/BDUMP/dwhp_pmon_1912834.trc:
This will also dump a systemstate dump and the location will be mentioned in alert.log
Also at OS level, we see that MMAN is consuming lot of CPU.
.
Cause
This issue was worked upon by development in
Bug 6488694 - DATABASE HUNG WITH PMON FAILED TO ACQUIRE LATCH MESSAGE
Bug 6488694 was closed as a duplicate of Bug 7039896.
Solution
Apply the patch for Bug 7039896.
Issue is fixed in:
Workarounds that can be used:
Disable Automatic Shared Memory Management (ASMM) i.e Setting SGA_TARGET=0
or
Set the init.ora parameter _enable_shared_pool_durations=falseReferences
|
제품
|
||
관련 자료반응형
'ORACLE > TroubleShooting' 카테고리의 다른 글
| Memory Notification: Library Cache Object loaded into SGA (0) | 2012.03.06 |
|---|---|
| ora-4031 and shared pool duration (0) | 2011.12.28 |
| ORA-04031 (0) | 2011.12.06 |
| Share pool과 성능문제 (0) | 2011.12.06 |
| KGH: NO ACCESS" Memory Allocation (0) | 2011.11.23 |
