My Oracle Support Banner

imapd: Unable to Map Index file, Not Enough Space (Doc ID 1002194.1)

Last updated on MARCH 26, 2019

Applies to:

Oracle Communications Messaging Server - Version 5.1.0 and later
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86 (32-bit)
Linux x86


The error, "Critical Error:  ...  Out of space" or "Not enough space" occurs in your IMAP, POP or HTTP log files.  This may be associated with crashing, core dumping or slow performance and inability to log in.

<date/time> <hostname> imapd[<pid>] Store Critical: unable to map index file for user/<uid>; Not enough space
<date/time> <hostname> imapd[<pid>] Store Critical: unable to read index file for user/<uid>; system i/o error

In more recent releases, but still on the 32-bit version, you may see more explitict messages like:

<date/time> <hostname> imapd[<pid>] General Error: mmap failed for NNNNNN bytes: Cannot allocate memory
<date/time> <hostname> imapd[<pid>] General Critical: The process may be out of address space. Reduce service.imap.maxsessions to prevent this error (NNN sessions are currently active). service.imap.numprocesses may be increased to preserve overall capacity


On older versions, in the imta log file, you may see:



Typically, this is caused by general growth in your environment, including larger mail folders and more users logged in at the same time.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.