Instance Termination with ORA-07445 [ksl_get_shared_latch()+180] (Doc ID 2199283.1)

Last updated on NOVEMBER 22, 2016

Applies to:

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

Symptoms

1. Instance termination by ORA-07445 error.

2. Alert log contains following error

ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [ksl_get_shared_latch()+180] [SIGSEGV] [ADDR:0x125BE308C] [PC:0x101DC3B54] [Address not mapped to object] []
PMON (ospid: 10289572): terminating the instance due to error 602
...

3. Incident trace file shows failing statement related to DataPump activity (KUP...)

----- Current SQL Statement for this session (sql_id=gvkbyx5x9bcpv) -----
BEGIN sys.kupc$que_int.detach_queues(:1); END;

4. PL/SQL stack also shows AQ and DataPump packages:

----- PL/SQL Call Stack -----
object line object
handle number name
7000005277b84d8 765 package body SYS.DBMS_AQADM_SYSCALLS
7000003c7d0edf0 7531 package body SYS.DBMS_AQADM_SYS
700000525be65b8 441 package body SYS.DBMS_AQADM
70000051b3f7f98 1573 package body SYS.KUPC$QUE_INT
700000363986af8 223 package body SYS.KUPC$QUEUE_INT
700000363a83b60 1381 package body SYS.KUPV$FT_INT
70000051c558e60 4354 package body SYS.DBMS_DATAPUMP
70000051c558e60 1342 package body SYS.DBMS_DATAPUMP
70000051c558e60 3256 package body SYS.DBMS_DATAPUMP
70000051c558e60 4579 package body SYS.DBMS_DATAPUMP

5. Stack contains ksfglt

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