LMS waiting for 'SGA: allocation forcing component growth' and resulting in latch deadlock situation (Doc ID 1927064.1)

Last updated on JULY 07, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 to 12.1.0.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.
This mostly affects release 11.2.0.4

Symptoms

LMS waiting for 'SGA: allocation forcing component growth' and resulting in latch deadlock situation. Instance did not crash.

Excerpts from Database alert log

Wed Jun 04 08:04:26 2014
LMS0 (ospid: 20497) waits for event 'SGA: allocation forcing component growth' for 96 secs.
LMS1 (ospid: 20501) waits for event 'SGA: allocation forcing component growth' for 96 secs.
Errors in file
/u01/app/oracle/diag/rdbms/racdb_x16p/racdb1/trace/racdb1_lmhb_20511.trc  (incident=1152154):
ORA-29771: process PR09 (OSID 27535) blocks LMS0 (OSID 20497) for more than 70 seconds
Incident details in:
/u01/app/oracle/diag/rdbms/racdb_x16p/racdb1/incident/incdir_1152154/racdb1_lmhb_20511_i1152154.trc


A deadlock cycle can be seen from lmhb trace file.

racdb1_lmhb_20511.trc:

ORA-29771: process PR09 (OSID 27535) blocks LMS0 (OSID 20497) for more than 70 seconds

========= Dump for incident 1152154 (ORA 29771) ========
----- Beginning of Customized Incident Dump(s) -----
Process LMS0 (ospid: 20497) is waiting for event 'SGA: allocation forcing component growth'.
Process PR09 (ospid: 27535) is the blocker of the wait chain.
===[ Wait Chain ]===
LMS0 (ospid: 20497) waits for event 'SGA: allocation forcing component growth'.
MMAN (ospid: 20513) waits for event 'latch: cache buffers lru chain'.
PR09 (ospid: 27535) waits for event 'latch: gc element'.
DBW1 (ospid: 20517) waits for event 'latch: gcs resource hash'.
PR0I (ospid: 27553) waits for event 'latch free'.
PR0S (ospid: 27577) waits for event 'SGA: allocation forcing component growth'.
MMAN (ospid: 20513) waits for event 'latch: cache buffers lru chain'.
A cycle is detected.   <<<<


LMS short stack:

Short stack dump:
ksedsts()+465<-ksdxfstk()+32<-ksdxcb()+1927<-sspuser()+112<-__sighandler()<-__ poll()+47<-ssskgxp_poll()+40<-sskgxp_selectex()+392<-skgxpiwait()+4318<-skgxpwaiti()+1916
<-skgxpwait()+162<-ksxpwait()+2501<-ksliwat()+12633<-kslwaitctx()+163<-kmgs_sleep_wait()+191<-kmgs_create_request()+1150<-kmgs_immediate_req()+798
<-ksmasg()+171<-kghnospc()+1063<-kghalo()+1999<-kghxal()+193<-kjblextend()+148<-kjblralc()+360<-kjmxmpm()+1181<-kjmpbmsg()+4706<-kjmsm()+8034
<-ksbrdp()+1045<-opirip()+623<-opidrv()+603<-sou2o()+103<-opimai_real()+250<-ssthrdmain()+265<-main()+201<-__libc_start_main()+244

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms