Last updated on NOVEMBER 28, 2016
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
The following symptoms are known to be attributed to this issue :-
a) Database is 2 or more node RAC
b) The following error or similar is seen in the database alert log(s) :-
ORA-00600: internal error code, arguments: [ORA_NPI_ERROR], , [ORA-00603: ORACLE server session terminated by fatal error
ORA-00569: Failed to acquire global enqueue.
Session ID: 105 Serial number: 1
c) The database is managed by ASM instance(s) and ORA-04031 errors are observed in the ASM alert log(s) for example on the LMD0 process :-
ORA-04031: unable to allocate 3768 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","ges enqueues")
If the same ORA-600 error is seen on a non-RAC/ASM managed database this article might still be appropriate, if the same ORA-600 error is
seen on a non-ASM managed database this article does not offer a solution. The ORA-04031 error might be on a different process and might
have a different failed allocation request.
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