We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.
Showing posts with label Area. Show all posts
Showing posts with label Area. Show all posts

Checking Roll /Paging Area and Extended Memory using Transaction ST02 for SAP R/3

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

You can use Transaction ST02 to check if the buffers from the roll and paging areas are the same size as the paging files. By comparing the values under Max. use, you can check if the buffer size is large enough.

You can determine from the row Extended Memory that the R/3 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).





Keyword: BASIS
Title : Checking Roll /Paging Area and Extended Memory using Transaction ST02 for SAP R/3

R/3 Roll Area SAP

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Definition

The roll area is a memory area with a set (configurable) size that belongs to a work process. It is located in the heap of the virtual address space of the work process.

Use

When the context of a work process changes, the data is copied from the roll area to a common resource called the roll file. To prevent repeated copying, the data is buffered in the roll buffer which is located in the shared memory.

Structure

The roll area consists of 2 segments. The first segment, which can be set with the parameter ztta/roll_first, is assigned to the work process first as memory. If this is used up, the work process has more memory assigned to it. The amount of memory is determined by the difference between the parameters ztta/roll_area and ztta/roll_first.

See:

Allocating Memory for User Contexts

Integration

For technical reasons, the roll area is always the first memory that a work process receives. Only afterwards can Extended Memory be requested.

See: Virtual Address Space of a Work Process



Keyword: BASIS
Title : R/3 Roll Area SAP

Labels: , ,

SAP Memory Types :: Roll Area

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Keyword: BASIS
Title : SAP Memory Types :: Roll Area

Checking Roll /Paging Area and Extended Memory with Tcode ST02

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Keyword: BASIS
Title : Checking Roll /Paging Area and Extended Memory with Tcode ST02

ztta/roll_area: Roll Area

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Use

Total size of the roll area in bytes.

A part of this area (in the graphic Roll area 1) is allocated a user context at the beginning. Its size is defined in ztta/roll_first. The partial area is for the data that must be contained in the roll area. During a user context change, this data is "rolled" (copied) into and out of a work process. If ztta/roll_area is larger than ztta/roll_first, the additional space makes a second part available (Roll area 2).

If the user context cannot be allocated more Extended Memory, this second part of the roll area is available for the dialog processes (see Allocating Memory for User Contexts).

By specifying a higher value for ztta/roll_area than for ztta/roll_first, you avoid allocating local private memory as soon as the set limits of the R/3 Extended Memory are reached. The remaining roll memory therefore serves as the last buffer before a user context has to allocate heap memory.

This pushes back the point in time at which a work process is switched to PRIV mode (see Private Memory). Although there advantages to this procedure, there are also the following disadvantages: The copying procedure is much slower for storing data in the roll area for changing work process contexts. The copy necessary for the roll area during context changes is slower than the allocation procedure used for the context change with R/3 Extended Memory. Therefore, increasing the roll area memory slows down the context change.

Goal:

Reduce data transfer to a minimum using copy procedures during context changes (value closer to ztta/roll_first), higher values avoid problems however (address space, swap space, operating system paging, work process change to PRIV mode, if the R/3 Extended Memory limit is reached).

Integration

  • rdisp/ROLL_SHM: Should be adjusted if you change ztta/roll_area.
  • rdisp/ROLL_MAXFS: Must be adjusted if you change ztta/roll_area.
  • ztta/roll_area: Must be larger than or the same size as ztta/roll_first.

Activities

Unit: Bytes

Default value: 6500000 (6.5 MB)

Recommended value: UNIX: 6500000 (6.5 MB) 1000000 (1 MB) is the minimum size. Under IBM AS/400 167731120 (16 MB), under Windows NT: 1000000 (1 MB).

Changes: Under IBM AS/400, only SAP is allowed to change this value. Under UNIX and Microsoft Windows, you can only change this parameter value in accordance with the configuration examples (Contents button) or for Windows NT in accordance with the information in Maximum Use of Extended Memory.



Keyword: BASIS
Title : ztta/roll_area: Roll Area

ztta/roll_first: Initial Allocation Size from the Roll Area

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Use

This is the amount of roll memory allocated to a dialog work process before R/3 Extended Memory is allocated.

See Allocating Memory for User Contexts

Activities

Unit: Bytes

Default value: 1000000 (1 MB)

Recommended value: 1 (1 byte)

Under IBM AS/400: 167731120 (16 MB, value from ztta/roll_area).

One (1) byte means that only one small amount of memory specifically for that system is allocated and then goes in to the Extended Memory. If there is not a lot of Extended Memory available, a higher value (1 MB or higher) is useful (see Recognizing and Correcting Problems).

Changes: Under IBM AS/400, only SAP is allowed to change this parameter. Under UNIX and Microsoft Windows, you can only change this parameter value in accordance with the configuration examples (Contents button) or for Windows NT in accordance with the information in Maximum Use of Extended Memory.



Keyword: BASIS
Title : ztta/roll_first: Initial Allocation Size from the Roll Area

SAP MaxDB :: Displaying Information About the Log Area

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Keyword: BASIS
Title : SAP MaxDB :: Displaying Information About the Log Area

SAP MaxDB :: Displaying Information About the Data Area

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Keyword: BASIS
Title : SAP MaxDB :: Displaying Information About the Data Area

T r a n s l a t e to your language