[B] Database Crash Twice With Ora-7445 Ora-600 (Doc ID 1332021.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 13-Nov-2013***

Symptoms

Alert log reports next errors eventually leading to instance crash:

ORA-00600: internal error code, arguments: [17147], [0x53E48BB08], [], [], [], [], [], [], [], [], [], []

ORA-00600: internal error code, arguments: [17112], [0x53E48BB08], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [17147], [0x53E48BB08], [], [], [], [], [], [], [], [], [], []

ORA-00600: internal error code, arguments: [17114], [0x53E48BB08], [], [], [], [], [], [], [], [], [], []

found dead dispatcher 'D002', pid = (22, 1)

ORA-00600: internal error code, arguments: [KGHFRE3], [0x53E571420], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [KGHFRE3], [0x53E571420], [], [], [], [], [], [], [], [], [], []

PMON (ospid: 21051): terminating the instance due to error 472
Instance terminated by PMON, pid = 21051


The trace file shows following:

  Chunk        53e487a88 sz=     8256  NEXT NEXT CHUNK'S PREVIOUS POINTER NOT POINTING TO NEXT CHUNK 5443454a424f2e4f
  recreate  "KGLHD          "  latch=0

  Chunk        53e489ac8 sz=     8256  NEXT CHUNK'S PREVIOUS POINTER NOT POINTING TO CURRENT CHUNK 5443454a424f2e4f
  freeable  "NETWORK BUFFER "


The call stack in the trace file includes next functions:

... kgherror kghfrmrg kghfre kmnsbf nsbfr nscpxswap nsprecv nscon nsdo ...

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