PMON failed to acquire latch, see PMON dump Solution

PMON failed to acquire latch, see PMON dump solve the problem phenomenon: Database listening crash handling process: Database exception, after receiving the alarm, immediately log on to the server, lsnrctl status found that listener is dead, hurry up, the result lasted about 1 minute. The database can be connected and returns to normal. Next, find the cause of the problem and find an error in the alert Log: PMON failed to acquire latch, and see PMON dump. This is actually a BUG. Solution: the group discussion decides whether to install patches. Pmon Failed To Acquire Latch "Messages in Alert Log-Database Hung [ID 468740.1] In this DocumentSymptoms Cause Solution ReferencesThis 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 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 *** SymptomsDatabase 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 dumpFri Oct 5 10:33:00 2007 PMON failed to acquire latch, see PMON dumpFri Oct 5 10:34:05 2007 PMON failed to acquire latch, see PMON dumpErrors 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. on checking the system state dump, we see that MMAN is holding the Shared pool Latch and Location ofLatch is kgh_next_free or quiesce extents SO: 3df6835b8, type: 2, owner: 0, flag: INIT/-/0x00 (process) Oracle pid = 4, callcur/top: 3dfa94c48/3dfa94c48, flag: (6) SYSTEMint error: 0, call error: 0, sess error: 0, txn error 0 (post info) last post received: 0 0 0 24 (latch info) wait_event = 0 bits = 80 holding (efd = 3) 3800db408 Child shared pool level = 7 child # = 1 Location from where latch is held: kgh_next_free: Context saved from call: 0 state = busy, wlstate = freewaiter count = 3 Process Group: DEFAULT, pseudo proc: 3df77a4b8O/S info: user: oracle10, term: UNKNOWN, ospid: 25931OSD pid info: Unix process pid: 25931, image: oracle @ dbname (MMAN) short stack wocould be like javaskgh_next_free Syntax @ brief issue was worked upon by development in Bug 6488694-database hung with pmon failed to acquire latch MESSAGEBug 6488694 was closed as a duplicate of Bug 7039896. solutionPlease apply the patch 7039896 for your version and operating system. 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 PlatformsPlease refer toNote 7039896.8-Bug 7039896-Spin under kghquiesce_regular_extent holding shared pool latch with AMM Workarounds that can be used: Disable automation Shared Memory Management (ASMM) I. e Setting SGA_TARGET = 0-OR-Set the init. ora parameter _ enable_shared_pool_durations = falseReferencesBUG: 6488694-databse hung with pmon failed to acquire latch message note: 7039896.8-Bug 7039896-Spin under keep holding shared pool latch with AMM