My Oracle Support Banner

Instance Termination After ORA-07445 With core dump [kjdd_nodeadlock_chk()+180] [SIGSEGV] [ADDR:0x308A91FCC8] [PC:0x106C0F454] [Application data integrity precise] (Doc ID 2674178.1)

Last updated on MAY 27, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 18.6.0.0.0 to 18.6.0.0.0 [Release 18]
Information in this document applies to any platform.

Symptoms

Instance crash after lmd process reporting following ORA-07445 in instance alert log.

Tue Apr 28 00:00:54 2020 Exception [type: SIGSEGV, Application data integrity precise] [ADDR:0x308A91FCC8] [PC:0x106C0F454, kjdd_nodeadlock_chk()+180] [flags: 0x0,
count: 1]
Errors in file <ORACLE_BASE>/diag/rdbms/<DB_NAME>/<SID1>/trace/<SID1>_lmd0_140517.trc (incident=8005727):
ORA-07445: exception encountered: core dump [kjdd_nodeadlock_chk()+180] [SIGSEGV] [ADDR:0x308A91FCC8] [PC:0x106C0F454] [Application data integrity
precise] [7]
Incident details in: <ORACLE_BASE>/diag/rdbms/<DB_NAME>/<SID1>/incident/incdir_8005727/<SID1>_lmd0_140517_i8005727.trc
.

Tue Apr 28 00:01:20 2020
PMON (ospid: 140004): terminating the instance due to ORA error 482 

 Corresponding incident trace have following call stack.

<ORACLE_BASE>/diag/rdbms/<DB_NAME>/<SID1>/incident/incdir_8005727/<SID1>_lmd0_140517_i8005727.trc:

kjdd_nodeadlock_chk()+180<-kjddmr()+492<-kjddrr()+7568<-kjddind()+636<-kjmxmpm()+44648<-kjmpbmsg()+4036<-kjmdmain_0()+34168

 

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
Cause
Solution


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