cancel
Showing results for 
Search instead for 
Did you mean: 

Dump SYSTEM_NO_SHM_MEMORY

Former Member
0 Kudos

Hello:

For the second time in the last several months have appeared dump with

the following message SYSTEM_NO_SHM_MEMORY.

Can anybody help me?

Regards.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi:

Texto breve

No more memory for 1336 bytes in the shared objects memory.

¿Qué ha sucedido?

The shared objects memory is full or an area management specified

memory limit has be reached.

¿Qué puede hacer?

Try to find out (e.g. by targetted data selection) whether the

transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again.

-

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

Please make a note of the actions and input which caused the error.

-

To resolve the problem, contact your

SAP system administrator.

Select the "Print" function to obtain a hardcopy of the

current termination message.

Anál.errores

One of the following three situations has occurred:

1. In the shared objects memory there is not enough free memory

available for the storage of further data.

2. The maximum size specified in the area management for a version of

this area would be exceeded by the storage of further data.

3. The maximum size specified in the area management for all versions of

all instances of this area would be exceeded by the storage of

further data.

The data object was to be created in the following area instance:

"AREA=CL_SWF_CNT_FACTORY_SHMEM_AREAINST=CONTAINER_FACTORYCLNT=111"

Regards

Former Member
0 Kudos

Hi,

I got it.I faced almost a similar but slightly different issue.At the earliest open a customer message to SAP via

Go to SAP Marketplace -> Data Administration -> System Data -> Choose the system and update the info, the open the OSS message and if required open the system for SAP Support.

Use component BC-OP-NT.And in case SAP ask you to change any parameter via TCODE RZ10 dont forget to take the backup of you profile.As it might happen that the servers donot start after changing the parameter.In that case you have to restore this parameter for starting the server.

Open a customer and take precaution.Also read the note I send to you.

PS: Reward points to encourage us

Regards,

Ashutosh

Former Member
0 Kudos

Hi,

I would rather check the available space and probably tune the ztta/, abap/heap parameters and check the program for any expensive SQL statements(ST05).

Usually this will solve the problem. In case if you can't do so... you can contact SAP.

Regards,

Srihari

JPReyes
Active Contributor
0 Kudos

Just review your memory parameters.... specially abap/heap_area_dia, nondia and total.also review ES/SHM* parameters if you have any of them configured in your instance profile.

Regards

Juan

Former Member
0 Kudos

Hi,

Please paste your dump.If this is a low memory issue there is not much you can do prevent this issue except to select less data for the transaction or report that causes this issue.]

You can read SAP note 110172 and 552209.We face similar issue(i guess so).

Also send a customer message to SAP.They might help you better.

Regards,

Ashutosh

Edited by: ashutosh singh on Jul 23, 2008 1:49 PM

Former Member
0 Kudos

Hi,

Goto SNAPT table, Provide the dump in the ERRID field and execute. You will get the probable reasons as birds-eye-view...

If you can't figure out the problem., please paste the entire dump.

This is related to insufficient memory and the like.

In addition to this Check the note [972757|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=972757]

Regards,

Srihari

Edited by: Srihari Rao on Jul 23, 2008 3:38 PM