My Oracle Support Banner

Dispatcher Process Dies With ORA-600 [526] (Doc ID 1515890.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

  1. A dispatcher process dies with:
    ...
    ORA-00600: internal error code, arguments: [526], [0x0601093B0], [7], [shared pool], [5], [0x060109310], [4], [], [], [], [], []
    ...
    ORA-07445: exception encountered: core dump [nlqudeq()+80] [SIGSEGV] [ADDR:0x8] [PC:0x949AA48] [Address not mapped to object] []
    ORA-00600: internal error code, arguments: [526], [0x0601093B0], [7], [shared pool], [5], [0x060109310], [4], [], [], [], [], []
    ...
  2. Review of the generated tracefiles reveals a call stack similar to:
    ... <- ksl_level_check <- kslgetl <- ksfglt <- kghalo <- ...
  3. After an ORA-600 [526] in the dispatcher, sessions may hang waiting for 'library cache: mutex X'.

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.