My Oracle Support Banner

LMSK (ospid: xxxxx) has no Heartbeats for xx sec. (threshold 70) and LMS Hung While Dumping Buffers (Doc ID 2533042.1)

Last updated on OCTOBER 31, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

Instance hung while dumping buffers and terminate in Real Application Cluster environment.

alert_<instance>.log inside $ORACLE_BASE>/diag/rdbms/<DB_NAME>/<INSTANCE>/trace have following messages:


Thu Jan 24 08:10:32 2019
Dumping the buffer at level 1 instead of level 0   >>>>>>>>>>>>>>>>>>>>>>>>>
For full buffer dumps enable the following named event
alter session set events 'immediate trace name full_dumps level 1'
Thu Jan 24 08:11:56 2019
LMSK (ospid: 290409) has not called a wait for 84 secs.
Errors in file $ORACLE_BASE>/diag/rdbms/<DB_NAME>/<INSTANCE>/trace/<INSTANCE>_lmhb_290522.trc (incident=14425956):
ORA-29770: global enqueue process LMSK (OSID 290409) is hung for more than 70 seconds
Incident details in: $ORACLE_BASE>/diag/rdbms/<DB_NAME>/<INSTANCE>/incident/incdir_14425956/<INSTANCE>_lmhb_290522_i14425956.trc
Thu Jan 24 08:12:06 2019
LOCK_DBGRP: GCR_SYSTEST debug event locked group GR+DB_KPEX53 by memno 2
ERROR: Some process(s) is not making progress.
LMHB (ospid: 290522) is terminating the instance.
Please check LMHB trace file for more details.
Please also check the CPU load, I/O load and other system properties for anomalous behavior
ERROR: Some process(s) is not making progress.
LMHB (ospid: 290522): terminating the instance due to error 29770
Thu Jan 24 08:12:06 2019
opiodr aborting process unknown ospid (164135) as a result of ORA-1092
Thu Jan 24 08:12:06 2019
opiodr aborting process unknown ospid (163796) as a result of ORA-1092

<INSTANCE>_lmhb_290522.trc inside $ORACLE_BASE>/diag/rdbms/<DB_NAME>/<INSTANCE>/trace/:
*** ACTION NAME:() 2019-01-24 08:12:01.319

[TOC00000]
Jump to table of contents
Dump continued from file: $ORACLE_BASE>/diag/rdbms/<DB_NAME>/<INSTANCE>/trace/<INSTANCE>_lmhb_290522.trc
[TOC00001]
ORA-29770: global enqueue process LMSK (OSID 290409) is hung for more than 70 seconds

[TOC00001-END]
[TOC00002]
========= Dump for incident 14425956 (ORA 29770) ========
[TOC00003]
----- Beginning of Customized Incident Dump(s) -----
==================================================
=== LMSK (ospid: 290409) Heartbeat Report
==================================================
LMSK (ospid: 290409) has no heartbeats for 90 sec. (threshold 70)
: heartbeat state 0x2.ffff () pso-flag 0x100
: Not in wait; last wait ended 89 secs ago.
: last wait_id 330833546 at 'gcs remote message'.
==============================
Dumping PROCESS LMSK (ospid: 290409) States
==============================
===[ System Load State ]===
.
Load normal: Cur 9776 Highmark 368640 (38.18 1440.00)
===[ Latch State ]===
Not in Latch Get
===[ Session State Object ]===
..
service name: SYS$BACKGROUND
Current Wait Stack:
Not in wait; last wait ended 1 min 29 sec ago
Wait State:
fixed_waits=0 flags=0x20 boundary=(nil)/-1
Session Wait History:
elapsed time of 1 min 29 sec since last wait
0: waited for 'gcs remote message'
waittime=0x1e, poll=0x0, event=0x0
wait_id=330833546 seq_num=13067 snap_id=1
wait times: snap=0.000191 sec, exc=0.000191 sec, total=0.000191 sec
wait times: max=0.030000 sec
wait counts: calls=1 os=1
occurred after 0.000018 sec of elapsed time
1: waited for 'gcs remote message'
waittime=0x1e, poll=0x0, event=0x0
wait_id=330833545 seq_num=13066 snap_id=1
wait times: snap=0.000152 sec, exc=0.000152 sec, total=0.000152 sec
..
Short stack dump:

ksedsts()+244<-ksdxfstk()+58<-ksdxcb()+918<-sspuser()+224<-__sighandler()<-write()+16<-sdbgrfwf_write_file()+64<-dbgtfdFileWrite()+663 <-dbgtfdFileAccessCbk()+357<-dbgtfPutStr()+592<-dbktPri()+149<-ksdwrf()+551<-ksdwrfn()+187<-kcbzdh()+3528<-kcbdmp()+1488<-ktrgcm()+16836 <-ktrget2()+1269<-kclgeneratecr_main()+1470<-kclgeneratecr()+2924<-kclgcr()+1293<-kclcrrf()+1857<-kjblcrcbk()+1763<-kjblpcr()+374<-kjbmpbast()+3639 <-kjmxmpm()+864<-kjmpbmsg()+6392<-kjmsm()+19840<-ksbrdp()+1072<-opirip()+1488<-opidrv()+616<-sou2o()+145<-opimai_real()+270 <-ssthrdmain()+412<-main()+236<-__libc_start_main()+256

 

Changes

 No changes

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.