Wednesday, February 27, 2013

Solution to ORA-04030: out of process memory

Today I encountered following error, while trying to run "Purge Logs and Closed System Alerts" to purge data from "FND_LOG_MESSAGES" table.

ORA-04030: out of process memory when trying to allocate 82456 bytes (pga heap,control file i/o buffer)
ORA-04030: out of process memory when trying to allocate 16328 bytes (koh-kghu sessi,pmuccst: adt/record)

The values for the _PGA_MAX_SIZE and PGA_AGGREGATE_TARGET has been set to values even greater than the 4GB, but yet the same errors persist when 4GB is used.

The trace file also confirms that the process is limiting at 4GB.

4074 MB total:                                      
4072 MB commented, 192 KB permanent
1131 KB free (768 KB in empty extents),
4071 MB, 1 heap: "session heap "

These errors usually show up because of running out of map entries from the OS.
There are only 65536 memory map entries per process.


Change the upper limit at either the OS or at the database level:

  • Change the page count at the OS level:
by root user,
$ more /proc/sys/vm/max_map_count
$ sysctl -w vm.max_map_count=200000 (for example)
OR at database level,
  • Adjust the realfree heap pagesize within the database by setting the following parameters in the init/spfile and restart the database.

_realfree_heap_pagesize_hint = 262144
The default realfree allocator pagesize is 64 KB (65536) , so 64K entries take up 4GB. With 256KB (262144) pages, the limit goes to 16GB.


  1. Forgiving does not erase the bitter past. A healed memory is not a deleted memory. Instead, forgiving what we cannot forget creates a new way to remember. We change the memory of our past into a hope for our future. See the link below for more info.


  2. I have a great fun reading your blogs. You are really a great writer. Thank you for making this beautiful and awesome blogs. Hope to read more post from you in the future. Please dont forget to visit me in my site @ Thank you.


  3. The most effective method to Solve Oracle ORA-04030 Error Message through Remote DBA Services
    The Oracle Error ORA-04030 underwear that "Out of process memory" The ORA-04030 is a mix-up caused by an inadequacy of RAM on a committed (non-shared server) condition. Generally, the screw up is an "out of process memory" botch, where Oracle can't acquire the RAM anticipated that would complete the undertakings. It can in like manner be caused by too little of a Program Global Area (PGA) and by not setting parameters adequately considerable to allow enough RAM for taking care of. It is a run of the mill botch when running an import as well. The oversight can happen when trying to execute an outside movement or when running a data pump import.
    Contact to Online Oracle DB Support and Database Administration for Oracle to fathom this blunder.
    For More Info:
    Contact Number: 1-800-450-8670
    Email Address-
    Company’s Address- 507 Copper Square Drive Bethel Connecticut (USA) 06801