Skip to Content
avatar image
Former Member

Production dump STORAGE_PARAMETERS_WRONG_SET

Hi All,

We are getting below dump suddenly from last 2 days in our PRD system for one of critical FI report.No changes made to system and workload is also fine.

what could be the reason ?

Runtime Errors STORAGE_PARAMETERS_WRONG_SET

Date and Time 08.10.2007 10:30:38

ShrtText

&INCLUDE INCL_INSTALLATION_ERROR

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The program had already requested 185589040 bytes from the operating

system with 'malloc' when the operating system reported after a

further memory request that there was no more memory space

available.

Error analysis

When the program was running, it was established that more

memory was needed than the operating system is able to provide savely.

To avoid a system crash, you must prevent this

situation.

-


Last error logged in SAP kernel

-


Component............ "EM"

Place................ "SAP-Server lfyd043a_PRD_00 on host lfyd043a (wp 0)"

Version.............. 37

Error code........... 7

Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "

Description.......... " "

System call.......... " "

Module............... "emxx.c"

Best Regards,

AjitR

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Oct 08, 2007 at 06:56 PM

    What can you do?

    Make a note of the actions and input which caused the error.

    To resolve the problem, contact your SAP system administrator.

    You can use transaction ST22 (ABAP Dump Analysis) to view and administer

    termination messages, especially those beyond their normal deletion

    date.

    Set the system profile parameters

    - abap/heap_area_dia

    - abap/heap_area_nondia

    to a maximum of 185589040. Then reduce the value by 10.000.000 to be on the

    safe side.

    Then restart the SAP System.

    abap/heap_area_nondia and abap/heap_area_dia:

    Set smaller than the memory achieved for each process

    with 'malloc' and smaller than abap/heap_area_total

    You should also check whether the available memory (file system

    swap and main memory) is sufficient for the started program

    and its data.

    We have changed mentioned parameters and

    Below are current settings for parameters

    abap/heap_area_dia 2000000000 Byte Max. heap memory for dialog workprocesses

    abap/heap_area_nondia 2000001024 Byte Max. heap memory for non-dialog workprocesses

    Add comment
    10|10000 characters needed characters exceeded