Skip to Content

Memory Error dump "SYSTEM_NO_SHM_MEMORY'


Our new Web Dypro ABAP application in production is generating a memory error short dump. Since this is our 1st Web Dynpro ABAP application, we are not really familiar with the system tuning that may be necessary. Our basis group would like us to explore alternatives to increasing the shared abap memory allocation.

OSS note 972757 talks about how ABAP programmers can release shared objects locks with methods DETACH_COMMIT / DETACH_ROLLBACK .

Has anyone tried this? I am having trouble using these methods since the class u201CCL_SHM_AREAu201D is abstract. I seem to be a bit weak in the ABAP objects area.

Any suggestions will be appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Oct 20, 2008 at 08:06 PM

    Are you actually using Shared Memory in your application or is it just the little bit of the WD Framwork that is using Shared Memory?

    If it is just the framework, then this should need very much Shared Memory. I would say that if you are getting this message for just the framework then you should allocate a little bit more shared memory as your total allocation must be very small. What is your total shared memory size? The framework usage of shared memory can have a very positive impact on performance as the most commonly used functionality can be place in shared memory and reduce a large number of repetative processing. You can dispable the usage of Shared Memory with the Application Parameter WDSHAREDREPOSITORY - although I wouldn't suggest that unless absolutely necessary.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 20, 2008 at 08:04 PM

    Check note 1107298, see if that applies to you.

    We're on a 7.0 system though and had exactly the same issues, I've not been told how (and if) the Basis team found a definitive solution.

    What I've noticed is that the problem increases if you just reload applications with F5 instead of closing the browser and reopening.

    Hope this helps.


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 20, 2010 at 10:22 AM

    Go to transaction SHMA >Monitor>Select the all the area and click on Delete icon.

    Add comment
    10|10000 characters needed characters exceeded

    • >What's the consequence of deleting all the areas?

      That really depends upon the particular shared memory area and what the application is using it for. Generally shared memory is used to cache commonly used data and avoid duplicate calculations or database retrevals. This is how it is used in the WDA framework. Clearing the areas or turning off shared memory in the WDA framework can lead to performance problems, especially during startup.

      However other applications might be using shared memory for temporary storage or cross session communication. Clearing areas in these cases can lead to short dumps or data inconsistencies.