My Oracle Support Banner

11.2: ORA-07445 [kglbrk] In Shared Server Process (Doc ID 1533257.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Standard Edition - Version to [Release 11.2]
Information in this document applies to any platform.


In a RDBMS or database with shared server configuration, the following errors can be seen in the alert log file:

ORA-07445: exception encountered: core dump [kglbrk()+45] [SIGSEGV] [ADDR:0x30] [PC:0x93845E9] [Address not mapped to object]


ORA-7445: exception encountered: core dump [kglbrk()+44] [SIGSEGV] [ADDR:0x30] [PC:0x1085955EC] [Address not mapped to object] []


ORA-600: internal error code, arguments: [kglUnLock-bad-lock], [0x700000A09923FC8], [0], [0x7000009E8D9B330], [], [], [], [], [], [], [], [


According to incident file generated by errors:

The current session was recently idle sniped (the KSUSFTBD bit is set). For example:
      (session) sid: 1437 ser: 19495 trans: (nil), creator: 0x3e463e998
                flags: (0x81002e5) USR/- flags_idl: (0x2) -/TBD/-/-/-/-
                                                                                  ^^^--- flags here
   Cleanup details:
        Marked killed = 1 min 51 sec ago


The errors are occurring in shared servers processes:

This can be checked by looking at the trace file name: <instance_name>_s001_<process>_i<incident>.trc.
*_s001_* tells us this is a tracefile generated by a shared server process.


The call stack includes ksu_dispatch_tac, and might look similar to:

kglbrk <- kxsGetCursorStatus <- kxsFreeInactiveCursors <- ksu_dispatch_tac


To view full details, 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 a vibrant support community of peers and Oracle experts.