STORAGE_PARAMETERS_WRONG_SET (EM-Memory exhausted) error in NW04

Question

Hello experts,
We are having the following issue in our NW04 running on 32-bit Windows & Oracle 9.2 - report execution on the Portal, in BEx, or in RSRT frequently ends with the ST22 error STORAGE_PARAMETERS_WRONG_SET and text as copied below. At the same time our current parameters (also listed below) appear to be in line or even higher with SAP recommendations. Report design has also been optimized as per SAP suggestions and the overall data volume does not appear to be an issue as well. Have anyone experienced anything like that in BW or would have any suggestions? We have already gone through SAP note 779123 and related notes (546361, 552209, 110172) with no success. I have also seen some SDN posts regarding the error message, but so far nothing seems to apply to our case.
Any advice is greatly appreciated!
Profile parameter     Value          Unit
ztta/roll_area     2,000,000.00     Byte
ztta/roll_first     1.00          Byte
ztta/short_area     3,200,000.00     Byte
rdisp/ROLL_SHM     7,500.00          8 kB
rdisp/PG_SHM     7,500.00          8 kB
rdisp/PG_LOCAL     150.00          8 kB
em/initial_size_MB     6,500.00          MB
em/blocksize_KB     1,024.00          kB
em/address_space_MB     512.00     MB
ztta/roll_extension     2,000,683,008.00     Byte
abap/heap_area_dia     2,000,683,008.00     Byte
abap/heap_area_nondia     2,000,683,008.00          Byte
abap/heap_area_total                     2,000,683,008.00          Byte
abap/heaplimit     40,894,464.00          Byte
abap/use_paging     0.00          
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 242172048 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.
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 242172048. 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.
r analysis
When the program was running, it was established that more
memory was needed than the operating system is able to provide save
To avoid a system crash, you must prevent this
situation.
           Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server SAP-PBD_PBD_00 on host SAP-PBD (w
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV'
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1886

Answer 1

Hi Sudhir,
These settings need to be done by basis people. Anyhow, you can go to the tcode RZ11 and put in these parameters mentioned in the error message. There will be documentation available for these parameters. Try to see if the defaults are not met for any of these parameters. If you find something strange, report it to the basis. The documentations in this are very helpful. Hope this helps.
Thanks and Regards
Subray Hegde