MMAN terminated instance due to ORA-00600 [17074] (Doc ID 1137249.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.5 to 11.2.0.1 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 25-Oct-2013***

Symptoms

The Memory Management (MMAN) process experiences an ORA-00600 [17074] and then the instance is terminated.

The alertlog resembles similar to the following:

Tue Jun 22 03:18:48 2010
Errors in file /diag/rdbms/testdb/testdb/trace/testdb_mman_10544.trc (incident=422288):
ORA-00600: internal error code, arguments: [17074], [0x38EAA3FB0], [0x395E14BF0], [6], [], [], [], [], [], [], [], []
Incident details in: /oracle/diag/rdbms/testdb/testdb/incident/incdir_422288/testdb_mman_10544_i422288.trc
Tue Jun 22 03:18:49 2010
Errors in file /oracle/diag/rdbms/testdb/testdb/trace/testdb_mman_10544.trc:
ORA-00600: internal error code, arguments: [17074], [0x38EAA3FB0], [0x395E14BF0], [6], [], [], [], [], [], [], [], []
MMAN (ospid: 10544): terminating the instance due to error 822
Instance terminated by MMAN, pid = 10544


The resultant trace file confirm the following call stack:

... kglhpd_internal kghrecr_quiesce kghquiesce_regular_extent kgh_next_free ...

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