on 07-06-2011 3:19 PM
Hi All
My enviroment is ERP6.0/Oracle 10.2.0.2/Solaris 10 SPARC 64bit.
Of late there have been memories issues with the DEV system which is hanging on a regular basis. A check at ST22 show this error 06.07.2011 14:59:26 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
The SAP system is installed on a unified storage. In my internal disk I'm short of space for creating an additional swap file & I'm thinking of creating a 20GB filesystem on the storage for swap . Is it OK if I configure swap file in the external disk (storage) ?
below is the output of df -h of my disk
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d30 7.2G 4.2G 2.9G 60% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 8.8G 1.1M 8.7G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
/dev/md/dsk/d32 4.8G 3.0G 1.8G 63% /usr
fd 0K 0K 0K 0% /dev/fd
/dev/md/dsk/d33 935M 447M 432M 51% /var
swap 9.8G 1.0G 8.7G 11% /tmp
swap 8.7G 40K 8.7G 1% /var/run
/dev/dsk/c6t60A98000572D4F6F4F345648496D4951d0s2
492G 215G 272G 45% /oracle
/dev/dsk/c6t60A98000572D4F6F4F345648496F6A62d0s2
39G 3.9G 35G 11% /sapmnt
/dev/dsk/c6t60A98000572D4F6F4F34564849687370d0s2
20G 12G 7.8G 60% /dev_archives
/dev/dsk/c6t60A98000572D4F6F4F345648496A6D6Dd0s2
9.8G 6.0G 3.7G 62% /logfiles
/dev/md/dsk/d71 4.9G 4.9G 0K 100% /sap
/dev/dsk/c6t60A98000572D4F6F4F34634C59625966d0s2
59G 35G 23G 60% /usr/openv
/dev/dsk/c6t60A98000572D4F6F4F34564849724D61d0s2
49G 19G 30G 40% /usr/sap
QAS:/usr/sap/trans 49G 25G 23G 53% /usr/sap/trans
Thanks
Hello,
Checkl note
425207 "SAP memory management, current parameter ranges",
regards,
John Feely
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> Of late there have been memories issues with the DEV system which is hanging on a regular basis. A check at ST22 show this error 06.07.2011 14:59:26 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
>
This error means that the application (workprocess) reached the maximum configured amount of memory.
This is not a storage or swap problem but solely a configuration problem.
I would first, before changing any parameters, contact the user who creates those dumps and ask him, if it's possible to reduce the amount of data. In most cases it's just a lack of selection criteria or people wanting to "download data" from SE16 or download huge spools from SP01.
If you need the have those programs ran through you need to adapt the parameters
abap/heap_area_dia (if it's a dialog process)
abap/heap_area_nondia (if it's a background process)
abap/heap_area_total
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response Markus
The dumps are created by system users ie DDIC, SAPSYS when running background jobs
Below is an extract of dump from ST22 for users DDIC & SAPSYS which are the source of the dumps
Information on where terminated
Termination occurred in the ABAP program "SAPLSHI2" - in
"STREE_READ_BUFFERED_DATA_GENER".
The main program was "SAPMS07A ".
In the source code you have the termination point in line 74
of the (Include) program "LSHI2U25".
The program "SAPLSHI2" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 13370305
-
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSEU_COMPONENT"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSEU_COMPONENT" - in
"RS_COMPONENT_VIEW".
The main program was "SAPMS07A ".
In the source code you have the termination point in line 35
of the (Include) program "LSEU_COMPONENTU01".
The program "SAPLSEU_COMPONENT" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 13401502
-
Client.............. 000
User................ "SAPSYS"
Language key........ "E"
Transaction......... " "
Program............. "SAPMSSY2"
Screen.............. "SAPMSSY2 4004"
Screen line......... 4
information on where terminated
Termination occurred in the ABAP program "SAPMSSY2" - in
"SELECT_TIME_TRIGGERED_JOBS".
The main program was "SAPMSSY2 ".
In the source code you have the termination point in line 527
of the (Include) program "SAPMSSY2".
The program "SAPMSSY2" was started as a background job.
Job Name....... " "
Job Initiator.. " "
Job Number..... " "
-
User and Transaction
Client.............. 001
User................ "PATCHER"
Language key........ "E"
Transaction......... " "
Program............. "RSBPCOLL"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSBPCOLL" - in "START-OF-SELECTION".
The main program was "RSBPCOLL ".
In the source code you have the termination point in line 40
of the (Include) program "RSBPCOLL".
The program "RSBPCOLL" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_JOBSTATISTIC"
Job Initiator.. "PATCHER"
Job Number..... 11320601
-
Secondly how do I adjust the two parameters below ?
abap/heap_area_nondia
abap/heap_area_total
These parameters cannot be adjusted dynamically from RZ11 and neither can I see them in the default, start & instance profiles when I ran transactions RZ10
Regards
Edited by: Andale Telewa on Jul 6, 2011 9:22 PM
Can you check how much memory is allocated at that time? This is also written in the dump.
Seems you started your monitoring jobs as user DDIC?
> -
> Secondly how do I adjust the two parameters below ?
> abap/heap_area_nondia
> abap/heap_area_total
>
> These parameters cannot be adjusted dynamically from RZ11 and neither can I see them in the default, start & instance profiles when I ran transactions RZ10
If you don't "see" them there, then they use the default of 2 GB. They are not dynmiacally changable in RZ11 but using the program RSMEMORY (start from SA38).
It would be interesting to see how much memory is allocated at the time they dump.
Markus
Markus
Forgot to tell you my physical RAM is 8GB & i have 3 swap files of sizes 8.8GB, 9.8GB & 8.7GB
Below is the info you requested
-
Error analysis
The internal table "\FUNCTION-POOL=STAM\FORM=NODETAB_FILL\DATA=LT_NODETAB_FULL"
could not be further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 2160
Number of rows: 0
Allocated rows: 4
Newly requested rows: 4372 (in 1093 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server DEV_DEV_01 on host DEV (wp 28)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1881
The error reported by the operating system is:
Error number..... " "
Error text....... " "
-
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 6221248
Extended memory (EM)........... 0
Assigned memory (HEAP)......... 2000960
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... 18446744058020205680
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLSEU_COMPONENT" or "LSEU_COMPONENTU01"
"RS_COMPONENT_VIEW"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
> Roll area...................... 6221248
> Extended memory (EM)........... 0
> Assigned memory (HEAP)......... 2000960
> Short area..................... " "
> Paging area.................... 32768
This is not much memory - so the reason for the dump is not (as usual) the 2 GB default setting but the fact, that there is no more memory available.
It seems that at the time that dump occurs another process/user is using up all the memory, the system tries to allocate more in the heap but failing because it is also used up.
The next time that dump happens check in ST02 the actual memory usage of extended and heap memory.
Markus
The dumps happen in quick succession & the system will hang continously for about 3 to 5 minutes. When this happens it will be virutally impossible at that moment to execute transaction st02. seet time stamps below from st22
current date Time App. Server username client keep Name of runtime error
06.07.2011 14:52:24 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:51:35 DEV_DEV_01 SAPSYS 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:51:05 DEV_DEV_01 DDIC 000 C TSV_TNEW_OCCURS_NO_ROLL_MEMORY
06.07.2011 14:51:05 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:51:05 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:51:04 DEV_DEV_01 SAPSYS 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:50:30 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:50:30 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:50:30 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:50:02 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:50:02 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:50:02 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:49:44 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:49:44 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:49:43 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:49:43 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:49:29 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:49:28 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:49:28 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:48:58 DEV_DEV_01 XXX3224 260 C TIME_OUT
06.07.2011 14:47:36 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:47:36 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:47:36 DEV_DEV_01 DDIC 000 C TSV_TNEW_PAGE_ALLOC_FAILED
06.07.2011 14:47:36 DEV_DEV_01 SAPSYS 000 C TSV_TNEW_PAGE_ALLOC_FAILED
is it prudent to adjust memory parameters using RSMEMORY ?
Thanks a
Just check how much memory is used in ST02 - not at the SAME time but around that time. how much extended and memory are allocated and how much is left?
Changing the parameter will most likely not change anything because there seems to be no more memory left. In fact this may increase the number of dumps.
Markus
Mackus
The situation has not recured but I'm sure it will before end of the day. I willl post those memory parameters immeidately after the system hangs
For the moment I've posted the extended & heap memory for the current time
SAP Memory Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
Roll area 3.41 8,947 45,464 131,072 131,072 IDs 99.59
Page area 0.36 951 102,816 65,536 196,608 Statement 96.00
Extended memory 5.08 212,992 360,448 4,190,208 0 0.00
Heap memory 11,082 0 560,921 0 0.00
Thanks
Below are the values of Extended Memory & heap memory when the problem recured this afternoon. Apologies about the formating. It doesnt seem to work here
SAP Memory Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
Roll area 4.36 11,420 45,464 131,072 131,072 IDs 99.82
Page area 2.03 5,326 102,816 65,536 196,608 Statement 96.00
Extended memory 8.60 360,448 491,520 4,190,208 0 0.00
Heap memory 180,885 0 560,921 0 0.00
AP Memory Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
oll area 11.10 29,091 45,464 131,072 131,072 IDs 99.82
age area 2.04 5,349 102,816 65,536 196,608 Statement 96.00
xtended memory 9.87 413,696 491,520 4,190,208 0 0.00
eap memory 182,850 0 560,921 0 0.00
SAP Memory Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
Roll area 12.69 33,273 45,464 131,072 131,072 IDs 99.82
Page area 1.97 5,165 102,816 65,536 196,608 Statement 96.00
Extended memory 11.14 466,944 491,520 4,190,208 0 0.00
Heap memory 171,768 0 560,921 0 0.00
SAP Memory Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
Roll area 7.60 19,936 45,464 131,072 131,072 IDs 99.83
Page area 1.58 4,137 102,816 65,536 196,608 Statement 96.00
Extended memory 9.87 413,696 491,520 4,190,208 0 0.00
Heap memory 34,509 0 560,921 0 0.00
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.