My Oracle Support Banner

Instance crashed with ORA-00600 [kglGetMutex], ORA-00600 [kglpnlt], ORA-07445 [kglhdgn()+282], ORA-07445 [kglGetMutex()+80] (Doc ID 1965666.1)

Last updated on AUGUST 25, 2023

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.3 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.

Symptoms

Alert log reports internal errors like below:

    ORA-00600: internal error code, arguments: [kglGetMutex], [], [], [], [], [], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [kglpnlt], [], [], [], [], [], [], [], [], [], [], []
    ORA-07445: exception encountered: core dump [kglhdgn()+282] [SIGSEGV] [ADDR:0x0] [PC:0x93908AA] [SI_KERNEL(general_protection)] []
    ORA-07445: exception encountered: core dump [kglGetMutex()+80] [SIGBUS] [ADDR:0xF67D5310] [PC:0x9392516] [Non-existent physical address] []


The call stack from the trace file includes functions like:

... kglGetMutex kglScanHandles4Unke ktmmon ep ktmSmonMain ksbrdp opirip opidrv ...

Note: Here the call stack is similar for ORA-00600 [kglGetMutex] and ORA-07445 [kglGetMutex()+80].


During analysis, following Note 13550185.8, it was found that CURSOR_SHARING=EXACT and SYS_Bnnn binds were used in SQL statements.

This was confirmed from the incident trace file and by executing below SQL statement in customer environment:

 

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.