My Oracle Support Banner

Database Instance Crashes with ORA-7445[dbgdLookupEventNode()+413] when Enabling Events in CDB and PDB (Doc ID 2575436.1)

Last updated on FEBRUARY 28, 2020

Applies to:

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

Symptoms

After enabling events in a multitenant environment:

SQL> connect / as sysdba
SQL> alter system set events 'sql_trace [sql:1111111111111] wait=true,bind=true';
SQL> alter session set container=<PDB_NAME>;
SQL> alter system set events 'sql_trace [sql:1111111111111] wait=true,bind=true';

the instance crashes with the following error in the alert log:

ORA-07445: exception encountered: core dump [dbgdLookupEventNode()+413] [SIGSEGV] [ADDR:0x7F58E85F9EB0] [PC:0x40BE03D] [Address not mapped to object] []

 

The Call Stack Trace in the associated incident trace file shows:

ksedst <- dbkedDefDump <- ksedmp <- ssexhd <- sslssSynchHdlr
 <- sslsshandler <- sighandler <- dbgdLookupEventNode <- dbgdSyncEventGrpsDi <- rect
  <- dbkdSyncSysTac <- kpdbugnfy <- ksmuin <- ksucre <- kxfpProcessJoin
   <- 565 <- kxfpProcessMsg <- kxfpqidqr <- kxfprdp_int <- opirip
    <- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main
     <- libc_start_main <- start

 

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.