PMON failed to ac…

 

Syn:

 

shutdown immediate命令卡住，数据库HANG无法关闭

 

Wed Dec 18 21:06:22 2013
Starting background process EMN0
EMN0 started with pid=24, OS id=25781
Wed Dec 18 21:06:22 2013
Shutting down instance: further logons disabled
Wed Dec 18 21:06:23 2013
Stopping background process CJQ0
Wed Dec 18 21:06:23 2013
Stopping background process QMNC
Wed Dec 18 21:06:25 2013
Stopping background process MMNL
Wed Dec 18 21:06:26 2013
Stopping background process MMON
Wed Dec 18 21:06:27 2013
Shutting down instance (immediate)
License high water mark = 66
Wed Dec 18 21:06:27 2013
Stopping Job queue slave processes
Wed Dec 18 21:06:27 2013
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Wed Dec 18 21:06:33 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Wed Dec 18 21:06:43 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Wed Dec 18 21:06:54 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Wed Dec 18 21:07:04 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Wed Dec 18 21:07:14 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Wed Dec 18 21:07:24 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Wed Dec 18 21:07:35 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Wed Dec 18 21:07:45 2013
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump

 

 

 

Pmon Failed To Acquire Latch" Messages in Alert Log -DatabaseHung (文档 ID 468740.1)转到底部

---

修改时间:2013-8-21类型:PROBLEM

In thisDocument

SymptomsCauseSolutionReferences

---

This document is being delivered to you via OracleSupport's Rapid Visibility (RaV) process and therefore has not beensubject to an independent technical review.

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.7[Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 26-Apr-2012***

Symptoms

Database Instance hangs and connections to database using'sqlplus' are also not possible.

Checking alert.log we see following messages

PMON failed to acquirelatch, 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 bementioned in alert.log

Also at OS level, we see that MMAN is consuming lot of CPU.

On checking the system state dump, we see that MMAN is holding theShared pool Latch and Location of
Latch is kgh_next_free or quiesce extents

SO: 3df6835b8, type: 2, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=4, calls cur/top: 3dfa94c48/3dfa94c48, flag:(6)
SYSTEM
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 24
(latch info) wait_event=0 bits=80
holding (efd=3) 3800db408 Child shared pool level=7child#=1
Location from where latch is held:kgh_next_free:
Context saved from call: 0
state=busy, wlstate=free
waiter count=3
Process Group: DEFAULT, pseudo proc: 3df77a4b8
O/S info: user: oracle10, term: UNKNOWN, ospid: 25931
OSD pid info: Unix process pid: 25931, image: oracle@dbname(MMAN)


Short stack would be like below
kghquiesce_regular_extent kgh_next_freeksmc_next_free kmgs_extract_mem_from_granule@kmgs_check_inuse_lists

Cause

This issue was worked upon by developmentin

Bug6488694 - DATABASE HUNG WITH PMON FAILED TO ACQUIRE LATCHMESSAGE

Bug 6488694 was closed as a duplicate ofBug7039896.

Solution

Please apply the patch 7039896 for your version and operatingsystem.

Issue is fixed in:

• 11.2.0.1 (Base Release)
• 10.2.0.5 (Server Patch Set)
• 10.2.0.4.1 (Patch Set Update)
• 10.2.0.4 Patch 22 on Windows Platforms

Please refer to
Note 7039896.8 - Bug 7039896 - Spin underkghquiesce_regular_extent holding shared pool latch with AMM


Workarounds that can be used:

• Disable Automatic Shared Memory Management(ASMM) i.e SettingSGA_TARGET=0
  
  - OR -
• Set the init.ora parameter_enable_shared_pool_durations=false