Checking Roll /Paging Area and Ext. Memory
with Trans. ST02 
Use
On the initial screen of transaction ST02 (Tune Summary) you can see the following overview of the SAP Memory underneath the Buffer overview.
SAP memory |
Current use |
Max. use |
In memory |
On disk
|
|
[%] |
[kB] |
[kB] |
[kB] |
[kB] |
|
Roll area |
5,47 |
448 |
1.280 |
8.192 |
0 |
Paging area |
0,01 |
16 |
72 |
9.600 |
252.544 |
Extended Memory |
4,03 |
6.144 |
22.528 |
152.576 |
0 |
Heap Memory |
0 |
0 |
0 |
0 |
0 |
This is a snapshot of the current (percentage and absolute values in kilobytes) and the maximum memory usage of the various SAP Memory Types. The table also indicates whether, and to what extent, the requirement is satisfied from the main memory and from the disk.
Procedure
You can determine from the Extended Memory row that the SAP Extended Memory is sufficiently large. The value [Max. use] is, in this example, noticeably smaller than the created memory area [In memory]. If both values are identical, you must increase the extended memory (profile parameter: em/initial_size_MB).
See also:
Private Memory (Heap Memory)