Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

sappfpar check

Hi All,

I wanted to understand the memory components that have been shown when we execute a sapfpar check

What is inside the pool and outside the pool.How does the shared memory get allocated.Thanks.

================================================================================

== Checking profile: SID_DVEBMGS63_hostname

================================================================================

Shared memory disposition overview

================================================================

Shared memory pools

Key: 10 Pool

Size configured.....: 152000000 ( 145.0 MB)

Size min. estimated.: 148139648 ( 141.3 MB)

Advised Size........: 152000000 ( 145.0 MB)

Key: 40 Pool for database buffers

Size configured.....: 162000000 ( 154.5 MB)

Size min. estimated.: 158351040 ( 151.0 MB)

Advised Size........: 162000000 ( 154.5 MB)

Shared memories inside of pool 10

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

Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.

Key: 13 Size: 60500000 ( 57.7 MB) Alert Area

Key: 14 Size: 20000000 ( 19.1 MB) Presentation buffer

Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring

Key: 17 Size: 11116480 ( 10.6 MB) Roll administration

Shared memories inside of pool 40

Key: 42 Size: 12512992 ( 11.9 MB) DB TTAB buffer

Key: 43 Size: 64574392 ( 61.6 MB) DB FTAB buffer

Key: 44 Size: 13374392 ( 12.8 MB) DB IREC buffer

Key: 45 Size: 6206392 ( 5.9 MB) DB short nametab buffer

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

Key: 47 Size: 8193024 ( 7.8 MB) DB CUA buffer

Key: 48 Size: 500000 ( 0.5 MB) Number range buffer

Key: 49 Size: 2968344 ( 2.8 MB) Spool admin (SpoolWP+DiaWP)

Shared memories outside of pools

Key: 1 Size: 2500 ( 0.0 MB) System administration

Key: 2 Size: 6253276 ( 6.0 MB) Disp. administration tables

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

Key: 4 Size: 517648 ( 0.5 MB) statistic area

Key: 6 Size: 532480000 ( 507.8 MB) ABAP program buffer

Key: 7 Size: 14838 ( 0.0 MB) Update task administration

Key: 8 Size: 268435556 ( 256.0 MB) Paging buffer

Key: 9 Size: 583270500 ( 556.2 MB) Roll buffer

Key: 18 Size: 3670116 ( 3.5 MB) Paging adminitration

Key: 19 Size: 50000000 ( 47.7 MB) Table-buffer

Key: 30 Size: 27648 ( 0.0 MB) Taskhandler runtime admin.

Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue

Key: 33 Size: 20480000 ( 19.5 MB) Table buffer, part.buffering

Key: 34 Size: 33554432 ( 32.0 MB) Enqueue table

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

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

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

Key: 54 Size: 8396800 ( 8.0 MB) Export/Import buffer

Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist

Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared mem

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

Key: 62 Size: 377487360 ( 360.0 MB) Memory pipes

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

Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.

Key: 65 Size: 8396800 ( 8.0 MB) Export/Import Shared Memory

Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0

Key: 58900163 Size: 4096 ( 0.0 MB) SCSA area

Nr of operating system shared memory segments: 29

Shared memory resource requirements estimated

================================================================

Total Nr of shared segments required.....: 29

System-imposed number of shared memories.: 1000

Shared memory segment size required min..: 583270500 ( 556.2 MB)

System-imposed maximum segment size......: 21340618752 (20352.0 MB)

Swap space requirements estimated

================================================

Shared memory....................: 2157.1 MB

..in pool 10 141.3 MB, 97% used

..in pool 40 151.0 MB, 97% used

..not in pool: 1855.7 MB

Processes........................: 349.2 MB

Extended Memory .................: 5968.0 MB

-


Total, minimum requirement.......: 8474.3 MB

Process local heaps, worst case..: 1907.3 MB

Total, worst case requirement....: 10381.6 MB

Errors detected..................: 0

Warnings detected................: 0

Former Member
Former Member replied

Hi Ambarish,

in the past, many operating systems had limitations on the total number of possible shared memory segments. Therefore SAP invented the shared memory pools, which they called arbitrarily pool 10 and pool 40. So the SAP software takes care of the internal structure of the shared memory segments pool 10 and pool 40. Both are just ordinary shared memory segments for the operating system. The SAP software knows that inside shared memory segment "pool 10" there are the SAP shared memory segments with Key 11, 12, 13, 14, 16, 17. Similarily in shared memory segment called "pool 40" there are SAP shared memory segments with Key 42, 43, 44, 45, 46, 47, 48, 49.

As usual, SAP is quite flexible so you can configure this assignement and remove some keys from a pool or put other keys inside a pool. Nowadays the limits from the operating systems do not apply any more so we could do without pool 10 and 40 and have for each SAP memory segment a dedicated operating shared memory segment.

I hope this makes the situation clearer for you.

Regards,

Mark

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question