MMON Consuming a Huge Amount of Memory Raising ORA-4030 and Causing an Instance Hang
Last updated on NOVEMBER 28, 2016
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Information in this document applies to any platform.
***Checked for relevance on 12-Nov-2013***
The MMON process gathers a huge amount of memory while doing an Auto-Flush Slave Action, before raising an ORA-4030 error and hanging the database instance. The instance may need to be restarted in order to solve this problem.
The MMON trace file shows most of the used memory was free but not released, as in:
14 GB commented, 201 KB permanent
1398 MB free (832 KB in empty extents),
15 GB, 1764740 chunks: "kgh stack " 1395 MB free held
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