Skip to Content
avatar image
Former Member

MEM_ALLOC_FAILED dump when exporting data to excel

Hello All

We are getting dump for a particular user in our ECC Production system, when the user tries to export some data from SQ00 transaction.

Steps to reproduce the issue :

SQ00 -> User group (Material Management) -> Select a query -> run with variant.

Then click ok.

Here its redirects to you a screen where we just specify details of the plant and date which is for three to four months. Then execute in dialog. The process takes around 5-10 mins to run.

After this details are displayed on screen. Then we export to excel in the local dekstop. During this process it ends with a dump ( MEM_ALLOC_FAILED ).

The same when executed by other users, It works.

Please advise us on this



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jan 30, 2017 at 06:15 PM


    Are you sure this isn't related to the memory allocation issues you're reporting at If so, it may be best to solve this all in one thread, as it certainly seems similar. Over there, Isaias pointed you toward some good resources for troubleshooting memory issues in NetWeaver 7.4+ systems. Questions about MEM_ALLOC_FAILED and/or TSV_TNEW_PAGE_ALLOC_FAILED come up all the time, so you might try searching on it.

    ST02 is a good resource for starting your troubleshooting. Restarting your instance is a bad idea (assuming this is production) unless your system is basically hung and no one can work anyway.

    Have a look at:

    Note 1680814: "EmAllocFailed" and other memory allocation problems


    Add comment
    10|10000 characters needed characters exceeded

  • Feb 01, 2017 at 07:53 AM

    Hi Sub,

    When checking a memory dump (in this case, MEM_ALLOC_FAILED) you can always check on the dump itself the amount of memory that was being consumed at that timestamp.
    Dump shows: "The amount of memory (in bytes) used at termination time was: "

    It's also always recomendable to check information written on the affected work process trace file (dev_w*). You can find on the dump which was the affected work process, under 'System environment' section:
    Application server... <server_name>
    Work process number... <nr>

    This helps to get a general overview about the reason of this dump,as memory shortage can be caused by many different reasons. ST02 is also a good starting point to check memory health on each application server.
    For deeper analysis, please attach complete dump and check information written on corresponding work process trace file.


    Add comment
    10|10000 characters needed characters exceeded

  • Jan 29, 2017 at 06:59 AM

    Hi Sub.

    1. During the process check the buffers status in transaction code ST02? if possible do the restart the SAP instance.

    2. Could you share the full dump as text format attachment?



    Add comment
    10|10000 characters needed characters exceeded