Runtime Errors STORAGE_PARAMETERS_WRONG_SET

Question

Hi,
My functional team had run customized program in dialog, but after few minutes the error occured as below:-
Runtime Errors STORAGE_PARAMETERS_WRONG_SET
What happened?
The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 344148608 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 344148608. Then reduce the value by 10.000.000 to be on the
safe side.
Then restart the SAP System.
SAP Release.............. "620"
Application server.......
Network address..........
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x Intel 80686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 15
Short dump setting....... "full"
Database server..........
Database type............ "MSSQL"
Database name............ "PRD"
Database owner........... "prd"
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Then we try run in background job, but error occurred show as below:-
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
       Occurred on     25.03.2010 at 16:51:02
No storage space available for extending the internal table.
What happened?
You attempted to extend an internal table, but the required space wa
not 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 admini
termination messages, especially those beyond their normal deletion
date.
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 addr
       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.
I had check parameter value in RZ10 and below is the result:-
1.abap/heap_area_dia = 2000683008
2.abap/heap_area_dia = 2000683008
3. ztta/roll_area = 2000896
4.ztta/roll_extension   = 2000683008
5.abap/heap_area_total   = 2000683008
6.em/initial_size_MB = 20000
I need advice on this.
Thank you
Regards,
Anang78
Edited by: anang78 on Mar 25, 2010 10:14 AM

Answer 1

Hi,
Your customized program execution is demanding more heap memory. It may be pointing to memory re-configuration.
Please refer the following SAP Notes and compare your exiting memory parameter settings and do the adjustment according to the available RAM.
[SAP Note 425207 - SAP memory management, current parameter ranges|https://service.sap.com/sap/support/notes/425207]
[SAP Note 88416 - Zero administration memory management as of 4.0A/ Windows|https://service.sap.com/sap/support/notes/88416]
Also analyze the execution of that Customized Program, weather the Coding is optimized, weather the program is executing any Expensive SQL Statement or not.
Refer SAP Note 129813, one alternative is mentioned to deal with this memory related issue by activating 3GB feature in your existing Windows OS. Please refer Microsoft KB article 283037 and KB 268363 for the same. You will have to edit your boot.ini file to append /PAE switch.
Regards,
Bhavik G. Shroff