on 05-28-2010 9:45 AM
Sol. Man. dump STORAGE_PARAMETERS_WRONG_SET
Hi experts,
We are facing the following problem in our SM system - SM 7.0 with EhP1 SPS 06. When certain transactions are started a short dump is generated with error text STORAGE_PARAMETERS_WRONG_SET. This is a part of the dump text:
What happened?
The current program had to be terminated because of an error when installing the R/3 System.
The program had already requested 1 382 466 704 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 safely to provide. To avoid a system crash, you must prevent this situation from occurring.
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server ... on host ... (wp 3)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1897
The error reported by the operating system is:
Error number..... " "
Error text....... " "
System environment
SAP-Release 701
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 80686"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database type..... "ADABAS D"
Char.set.... "English_United State"
SAP kernel....... 701
created (date)... "May 16 2010 22:55:15"
create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.0.035 CL 139084 "
Patch level. 93
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7, MaxDB 7.8"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0, Windows NT 6.1"
Memory consumption
Roll.... 2609360
EM...... 382578336
Heap.... 1382466704
Page.... 57344
MM Used. 1708544512
MM Free. 54755528
Edited by: Petar Yordanov on May 28, 2010 11:47 AM
The only way to fix the problem is migrating to a 64-bit system as 32-bit system cannot address as much memory as needed to some of the transactions/reports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Petar.
Can you please review and apply the following notes:
88416 Zero administration memory management as of 4.0A/ Windows
110172 Windows: Transactions with large storage requirements
After the changes to the profile, please restart the instance for the
new setting to take effect.
This should resolve this short dump.
Regards,
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Paul,
Thanks for the suggestions!
The first SAP note 8... is already implemented (all parameters in the profile are set according it).
The second one 11... is applicable to other versions of Windows Server 2003 (Enterprise or Datacenter - /PAE parameter in boot.ini) - our OS is 32-bit Windows Server 2003 Standard Edition, and we have already set the /3GB parameter in boot.ini.
The problem still persists.
Best regards,
Petar
The system is installed on OS Windows Server 2003 SE 32-bit with 3 GB RAM and MaxDB 7.6.00.035. 9 GB are reserved for the pagefile.
We have set the /3GB parameter in boot.ini too.
Is there anything we can do to solve the problem, except the migration to 64-bit system?
Best regards and many thanks,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
These are some of the profile parameters of the system:
Parameter Name System Default Value System Default Value(Unsubst. Form) User-Defined Value
EM/TOTAL_SIZE_MB 262144 262144
PHYS_MEMSIZE 3071 3071 2048
abap/NTfmode t t
abap/aab_log_field_size_limit 1024 1024
abap/atrasizequota 30000 30000
abap/buffersize 300000 300000
abap/cache_area 1000000 1000000
abap/heap_area_dia 2000000000 2000000000
abap/heap_area_nondia 2000000000 2000000000
abap/heap_area_total 2000000000 2000000000
abap/heaplimit 40000000 40000000
abap/programs 100 100
abap/pxa shared shared
abap/pxaclients 32 32
abap/restricted_dset_open yes yes
abap/rsyntextln 180000 180000
abap/rtm_high_water 1038336 1038336
abap/rtm_memory1_size 25000 25000
abap/rtm_memory2_size 25000 25000
abap/rtm_memory3_entries 1000 1000
abap/set_textenv/ignore_errors 0 0
abap/set_textenv/skip_all 0 0
abap/shared_objects_size_MB 20 20
abap/slin_intcheck off off
abap/string_sharing on on
abap/super open open
abap/swap_reserve 20000000 20000000
abap/table_sharing on on
abap/timeout 512 512
abap/unicode_check off off
abap/use_max_bcd 0 0
abap/use_mm 1 1
abap/use_paging 0 0
abap/warn2error_release 700 700
em/address_space_MB 512 512
em/as4/max_free_list -1 -1
em/blocksize_KB 1024 1024
em/execute_protection TRUE TRUE
em/global_area_MB 128 128
em/initial_size_MB 2048 2048
em/max_dump_lines 6291456 6291456
em/max_size_MB 20000 20000
ztta/cua_area 250000 250000
ztta/diag_area 250000 250000
ztta/dynpro_area 800000 800000
ztta/hold_data_area 2000 2000
ztta/max_memreq_MB 250 250
ztta/parameter_area 16000 16000
ztta/roll_area 2000000 2000000 3000000
ztta/roll_extension 2000000000 2000000000
ztta/roll_extension_dia 2000000000 $(ztta/roll_extension) 2000000000
ztta/roll_extension_nondia 2000000000 $(ztta/roll_extension) 2000000000
ztta/roll_first 1 1
ztta/short_area 1600000 1600000
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.