TSV_TNEW_PAGE_ALLOC_FAILED at SEM BCS

[Former Member]

Hey SAP-Admins !<p>

I have a Problem with this shortdump TSV_TNEW_PAGE_ALLOC_FAILED at TA: UCWB_INT<p>

We're running Windows 64 Bit / SAP + DB with 24 GB RAM and 30 GB swap space.<p>

I don't understand why we got this dump cause cause we have ZAMM aktiv and only the<p>

memory parameter <p>

Phys_memsize = 8192<p>

abap/use_paging = 0 <p>

abap/heaplimit = 408944640 <p>

abap/swap_reserve = 20971520 <p>

em/blocksize_KB = 1024 <p>

abap/shared_objects_size_MB = 600 <p>

rdisp/max_wprun_time = 3600 <p>

aktiv.<p>

memorystate on the OS-System at the Dump<p>

http://i53.tinypic.com/zlexjc.jpg<p>;

output memlimits<p>

D:\usr\sap\B07\SYS\exe\nuc\NTAMD64>memlimits -v off<p>

SAP R/3 address space configuration test tool V3.2 (98/01/14)<p>

=========================================================================<p>

Verbose mode off<p>

Check the maximum data size per process (malloc)<p>

Maximum process heap size = 4096MB<p>

----

---

<p>

| Result |<p>

----

---

<p>

Maximum heap size per process........: 4096 MB<p>

measurement limited to 4096 MB<p>

this value is probably limited by swap space<p>

Total available swap space...........: 4096 MB<p>

measurement limited to 4096 MB<p>

main memory size x 3 recommended , minimum 1 GB<p>

swap space probably even bigger, but cannot be<p>

totally allocated by only one process<p>

output sappfpar<p>

D:\usr\sap\B07\SYS\exe\nuc\NTAMD64>sappfpar check pf=D:\usr\sap\B07<p>

\SYS\profile\<p>

B07_DVEBMGS00_SAPBON1S22<p>

================================================================================<p>

== Checking profile: D:\usr\sap\B07<p>

\SYS\profile\B07_DVEBMGS00_SAPBON1S22<p>

================================================================================<p>

***WARNING: Unexpected parameter: login/password_max_new_valid =0<p>

***WARNING: Unexpected parameter: login/password_max_reset_valid =0<p>

Shared memory disposition overview<p>

================================================================<p>

Key: 1 Size: 2500 ( 0.0 MB) System administration<p>

Key: 2 Size: 5503580 ( 5.2 MB) Disp. administration<p>

tables<p>

Key: 3 Size: 13714400 ( 13.1 MB) Disp. communication areas<p>

Key: 4 Size: 519448 ( 0.5 MB) statistic area<p>

Key: 5 Size: 4096 ( 0.0 MB) SCSA area<p>

Key: 6 Size: 362086400 ( 345.3 MB) ABAP program buffer<p>

Key: 7 Size: 14838 ( 0.0 MB) Update task administration Key: 8 Size: 134217828 ( 128.0 MB) Paging buffer<p>

Key: 9 Size: 268435556 ( 256.0 MB) Roll buffer<p>

Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer<p>

Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert<p>

Buf.<p>

Key: 13 Size: 40500000 ( 38.6 MB) Alert Area<p>

Key: 14 Size: 4400128 ( 4.2 MB) Presentation buffer<p>

Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity<p>

monitoring<p>

Key: 17 Size: 2747780 ( 2.6 MB) Roll administration<p>

Key: 18 Size: 917604 ( 0.9 MB) Paging adminitration<p>

Key: 19 Size: 100000000 ( 95.4 MB) Table-buffer<p>

Key: 30 Size: 30720 ( 0.0 MB) Taskhandler runtime admin. Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue<p>

Key: 33 Size: 51200000 ( 48.8 MB) Table buffer,<p>

part.buffering<p>

Key: 34 Size: 16777216 ( 16.0 MB) Enqueue table<p>

Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer<p>

Key: 42 Size: 7056992 ( 6.7 MB) DB TTAB buffer<p>

Key: 43 Size: 32504728 ( 31.0 MB) DB FTAB buffer<p>

Key: 44 Size: 7914392 ( 7.5 MB) DB IREC buffer<p>

Key: 45 Size: 4842392 ( 4.6 MB) DB short nametab buffer<p>

Key: 46 Size: 20480 ( 0.0 MB) DB sync table<p>

Key: 47 Size: 4097024 ( 3.9 MB) DB CUA buffer<p>

Key: 48 Size: 300000 ( 0.3 MB) Number range buffer<p>

Key: 49 Size: 2769392 ( 2.6 MB) Spool admin<p>

(SpoolWP+DiaWP)<p>

Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.<p>

Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer<p>

Key: 54 Size: 4202496 ( 4.0 MB) Export/Import buffer<p>

Key: 55 Size: 8192 ( 0.0 MB) Spool local<p>

printer+joblist<p>

Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared<p>

mem<p>

Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset<p>

Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes<p>

Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory<p>

Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository<p>

Buf.<p>

Key: 65 Size: 41951232 ( 40.0 MB) Export/Import Shared<p>

Memory<p>

Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring<p>

V01.0<p>

Nr of operating system shared memory segments: 41<p>

Shared memory resource requirements estimated<p>

================================================================<p>

Total Nr of shared segments required.....: 41<p>

Shared memory segment size required min..: 362086400 ( 345.3 MB)<p>

Swap space requirements estimated<p>

================================================<p>

Shared memory....................: 1181.0 MB<p>

Processes........................: 247.4 MB<p>

Extended Memory .................: 4096.0 MB<p>

-

---

<p>

Total, minimum requirement.......: 5524.4 MB<p>

Process local heaps, worst case..: 8192.0 MB<p>

Total, worst case requirement....: 13716.4 MB<p>

Errors detected..................: 0<p>

Warnings detected................: 2<p>

D:\usr\sap\B07\SYS\exe\nuc\NTAMD64><p>

thank you a lot !<p>

Darius

[mercedes_fernandez]

Hello Darius,

in the shortdump you could see the amount of memory the program consumed till the dump, something like:

The amount of storage space (in bytes) filled at termination time was:

Roll area......................

Extended memory (EM)...........

Assigned memory (HEAP).........

then you see in the program reached the defined quotas per work process,

The sequence fo memory allocation in this scenario is:

1. Roll memory up to ztta/roll_first

2. Extended memory up to ztta/roll_extension or Extended memory exhausted

3. Roll memory remained: ztta/roll_area minus ztta/roll_first

4. Heap memory up to abap/heap_area_dia or Heap memory exhausted

When a Dialog work process or a Batch work process have used the memory

quotas the transaction / job will short dump

kind regards,

Mercedes

[Former Member]

Hey Mercedes, <p>

thank you for your answer! <p>

but this system are running with ZAMM configuration<p>

1. The basis for zero administration memory management on Windows is the dynamically self-extending extended memory. An "infinitely" large memory resource is made available with this method. The extended memory is initially set to the size of the profile parameter PHYS_MEMSIZE ([PM]). If more memory is required by the user, the extended memory extends itself in steps of "[PM] / 2" up to the set limit of the profile parameter em/max_size_MB (64 Bit 100000) or until the address space in the Windows page file is used up.<p>

In this case this DUMP is very strange cause there are no limits beside the PHYS_MEMSIZE parameter <p>

Roll area...................... 2417280 <p>

Extended memory (EM)........... 2000358240 <p>

Assigned memory (HEAP)......... 2000047808 <p>

Short area..................... " " <p>

Paging area.................... 942080 <p>

Maximum address space.......... " " <p>

best regards

Darius

[Former Member]

....but maybe this paramter em/address_space_MB = 4096 will limit the prozess !?

[mercedes_fernandez]

hello Darius,

but the extended memory is shared between all the work processes, to avoid that one work process could consume the

complete extended memory there are quotas per work process. Whith the ZAMM the quota limits are 2G as you can see in SAP Note 88416.

It looks that process reeached the parameter values

kind regards,

Mercedes

[Former Member]

Hi Mercedes, <P>

yeah you're right ! <p>

I thought the the ZAMM will auto extend this parameter now I changed the abap/heap_area_dia manual.

Tomorrow we'll see what's happen <p>

Thank you

Darius

Edited by: Darius Freliga on Oct 4, 2010 3:03 PM

[Former Member]

Can you provide a resolution to this issue (if one exists)? I'm receiving the same (or certainly very similar) short dump when executing BCS Load from Data Stream task.

Clearing the shared memory and then re-executing the task seems to fix the issue, but it's a work around that I'd like to stop having to perform.

[mercedes_fernandez]

Hello Jim,

you'd need to check how much memory has been consumed at the time of the dump. See my previous answer:

The amount of storage space (in bytes) filled at termination time was:

Roll area......................

Extended memory (EM)...........

Assigned memory (HEAP).........

then you see in the program reached the defined quotas per work process,

The sequence fo memory allocation in this scenario is:

1. Roll memory up to ztta/roll_first

2. Extended memory up to ztta/roll_extension or Extended memory exhausted

3. Roll memory remained: ztta/roll_area minus ztta/roll_first

4. Heap memory up to abap/heap_area_dia or Heap memory exhausted

When a Dialog work process or a Batch work process have used the memory

quotas the transaction / job will short dump

kind regards,

Mercedes

[Former Member]

Hi,

please increase your abap/heap_area_dia.

best regards

Darius