Last updated on MAY 15, 2016
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Information in this document applies to any platform.
Alert log reports internal errors like below:
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:
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:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms