Skip to Content


Dear Support ,

I am facing a technical problem that when we doing the CON2 transaction code , SAP made a shot-dump and showed me :


Occurred on 2010.04.08 at 11:19:25

>> Short dump has not been completely stored. It is too big.

No roll storage space of length 15936 available for OCCURS area.

And it told me to adjust below parameters in SAP :

o ztta/roll_area (1.000.000 - 15.000.000)

o ztta/roll_extension (10.000.000 - 500.000.000)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

o abap/heap_area_dia: (10.000.000 -

o abap/heap_area_nondia: (10.000.000 -

o em/initial_size_MB: (35-1200)

Does someone know how to fix this problem ? we are using SAP4.7 x 200 on 32bit windows 2003 platform .

I have checked the note "1351887" and '327116" , but it doesn't work ....

Thanks .

Best Regards,

Carlos Zhang

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Apr 08, 2010 at 05:08 AM


    SAP system Usage ?

    SAP system Kernel patch level ? I hope your SAP system is running with latest SAP kernel patch level. Sometime upgrading SAP Kernel with latest patch level may resolve such issue.

    Any other memory related dumps you are getting while executing other Transactions ?

    Please refer this SAP Note 425207 - SAP memory management, current parameter ranges and compare your current memory parameter settings with the recommendations mentioned for 32 bit system. Also refer this useful document [Optimizing the Memory Settings for SAP Systems on 32-Bit Windows|].

    Also refer the following SAP Notes to get more information.

    SAP Note 103747 - Performance: Parameter recommendations as of Release 4.0

    SAP Note 88416 - Zero administration memory management as of 4.0A/ Windows

    [Overview of Parameters for Windows|]


    Bhavik G. Shroff

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 05, 2010 at 09:51 AM


    Some additional information as SAP note 88416 should be in place:

    Zero administration memory management (Note #88416) generally

    over allocates roll and page memory. Usually you can reduce the

    the amounts allocated to the "in memory"

    rdisp/ROLL_MAXFS....Total amount of Roll (Filesystem+SHM); in 8KB block

    rdisp/ROLL_SHM......Shared memory element of Roll; in 8KB blocks

    rdisp/PG_MAXFS......Total amount of Page (Filesystem+SHM); in 8KB block

    rdisp/PG_SHM........Shared memory element of Page; in 8KB blocks

    =>Filesystem amount = MAXFS - SHM

    60MB or so each in memory should be sufficient. rdisp/ROLL_SHM &

    rdisp/PG_SHM only to be changed. This should allow extra

    memory space for process memory.

    These profiles would have to have be added to the instance profiles.

    You should monitor the roll and paging usage after this to ensure that

    more than 80% of each is never used as starting to use the paging

    and roll files very regularly when buffers are exhausted would have

    performance implications. You can check the history of each

    instance's usage of these areas by double-clicking on the values from

    the initial screen of ST02. This could potentially increase

    the available address space per process by about 260MB that would

    otherwise be wasted that will help avoid error with the buffer

    creation and otherwise allow more memory to be available for HEAP

    usage for larger memory intensive reports. These changes do not

    invalidate Zero Adminstration Memory Management usage but are merely

    tweaking the defaults further.


    Add comment
    10|10000 characters needed characters exceeded

  • May 05, 2010 at 04:41 PM


    See this note on your error

    353579 SYSTEM_NO_ROLL

    Double ztta/max_memreq_MB and restart system


    John Feely

    Add comment
    10|10000 characters needed characters exceeded