|
Share this post:
|
|
Goto transaction SCCL
give the source client (which you have to find size)
and the target client
then check test run
at the end you will see the size of client
|
Share this post:
|
|
Symptom
Under AIX, the heap memory may not exceed 256 MB. Extensive background processing jobs that exceed this limit may allocate R/3 Extended Memory; however, the Extended Memory may be used up.
Corrective action
Try to solve the problem using the following procedures. Note the sequence they are given in. If the problem cannot be corrected with one of these procedures, try the next procedure.
|
Share this post:
|
|
If the CCMS Alert Monitor or Transaction ST06 (see Monitoring the Status of the R/3 System) displays a high paging rate for the operating system, decrease the size of the roll and paging buffers (only Windows NT and UNIX). In the profile management of the CCMS, set the profile parameters rdisp/ROLL_SHM and rdisp/PG_SHM to 0. You must change the profiles used by the R/3 application servers on the relevant host system.
If free memory is available even during heavy system usage, or if there is only low paging activity, you can increase the size of the roll and paging buffers. This decreases the accesses to the hard disk caused by rolling and paging.
|
Share this post:
|
|
The data segment size restricts the size of a user context that is executed as an R/3 background job. The default value is 64 MB, which is however, not sufficient and should be increased. Set the data segment size for a process to the following values:
UNIX Operating System | Data Segment Size |
32 bit UNIX systems | Increase data segment size to approx. 600 MB. |
64 bit UNIX systems | Set data segment size to at least 2048 MB. |
Under IBM AIX, the maximum segment size is 256 MB; under Siemens-Nixdorf SINIX the maximum segment size is 384 MB.
You can check data segment sizes using the R/3 test program memlimits. (You must stop the R/3 server to do this.) Note the output row that appears as follows: Process xxxxx allocating. The segment size is displayed in the row Size = .
For more detailed information, also refer to the R/3 installation guide in the section covering UNIX kernel parameters.
|
Share this post:
|
|
Goto transaction SCCL, give the source client (which you have to find size)
and the target client then check test run at the end you will see the size of client
|
Share this post:
|
|
Use
In the SAP memory management system, the sizes of user contexts are gathered for statistical purposes. This parameter specifies the cycle in which the sizes are logged.
Only SAP is allowed to change this parameter.
|
Share this post:
|
|
Use
This value specifies the size of the segments that are assigned to the R/3 Extended Memory.
Only SAP is allowed to change this parameter.
Activities
Unit: 1 KB
Default value: 1024 (1 MB)
Recommended value: You may not change the default value.
|
Share this post:
|
|
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.
|
Share this post:
|
|
Use
This value specifies the size of the R/3 paging file in 8 KB blocks. The paging file functions as memory for extracts and exports to memory. See also: SAP Paging.
Goal:
Space must be sufficient; does not present a problem even if the dimensions are too large.
Integration
Space must be available in the file system.
Activities
Unit: 8 KB
Default value: 2048
Recommended value: UNIX: Optimally 32000, but the value depends on the server size. Under Microsoft Windows NT, it is the same size as rdisp/PG_SHM. Also note the configuration examples (Contents button). For more information on Windows NT, see Parameter Overview for Windows NT.
Absolute upper limit: 250000 blocks (2 GB) for special applications (file system must be large enough)
Changes: The customer can make changes.
|
Share this post:
|
|
Use
In the SAP memory management system, the sizes of user contexts are gathered for statistical purposes if the size exceeds the specified value.
Only SAP is allowed to change this parameter.
|
Share this post:
|
|
Use
This value specifies the size of the paging buffer in 8 KB blocks. Since Release 4.0, a paging buffer is no longer necessary for SAP Memory Management because internal tables and lists are not located in the R/3 paging.
Goal:
Value = 0, to save swap space
Activities
Unit: 8 KB
Default value: 0
Recommended value: UNIX: 1000, but the value depends on the server size and the host system. You can find the values in the configuration examples (Contents button). For more information on Windows NT, see Parameter Overview for Windows NT.
Absolute upper limit: 250000 blocks (2 GB) for special applications (file system must be large enough)
Changes: The customer can make changes.
|
Share this post:
|
|
Use
This value specifies the size of the roll file in 8 KB blocks. The roll file functions as memory for the part of the user contexts that finds space in the roll area.
Goal:
Space must be sufficient; problems should not occur even if the dimensions are too large.
Integration
Activities
Unit: 8 KB
Default value: 2.000; Under IBM AS/400: 0
Recommended values: Various values, depending on the server size If enough memory is available, under UNIX 64000 blocks.
Absolute upper limit: 250000 blocks (2 GB) for special applications (file system must be large enough)
Also note the configuration examples (Contents button). For more information on Windows NT, see Parameter Overview for Windows NT.
Changes: The customer can make changes.
|
Share this post:
|
|
Use
This value specifies the size of the roll buffer in 8 KB blocks.
The roll buffer functions as the cache for the roll file. For a fast change of context to occur, the roll areas of all user contexts should find space in the roll buffer (approximately 1 MB for each user).
Goal:
Minimum time for a context change
Integration
rdisp/ROLL_SHM : Buffered data is in the shared memory; accessing this data here is much faster than accessing a file.
For technical reasons, the roll buffer size must be at least 10% of the roll file size (parameter rdisp/ROLL_MAXFS: Maximum roll file size).
Activities
Unit: 8 KB
Default value: 0
Recommended value: UNIX: 8000, IBM AS/400: 0, under Microsoft Windows NT 128 blocks (1 MB)
Unless the Tune summary in the CCMS (Transaction ST02) (under Monitoring the Memory Management System) specifies that a larger roll buffer is required, do not set a value larger than 12500 (100 MB).
Absolute upper limit: 250000 blocks (2 GB) for special applications (file system must be large enough)
You can find the values in the configuration examples (Contents button). For more information on Windows NT, see Parameter Overview for Windows NT.
Changes: The customer can make changes.
|
Share this post:
|
|
Use
This value specifies the Extended Memory pool size that the R/3 System manages for the Extended Memory.
Goal:
Ideally, this pool is large enough to contain the sum of all the user contexts. The pool must always be larger than the size of the parameter ztta/roll_extension. This parameter specifies how much Extended Memory can be allocated to a user context.
If the pool is used up, heap memory is allocated (see Private Memory and Allocating Memory for User Contexts). The work process switches to the PRIV mode and is reserved exclusively for the current user context. After processing the user context, the work process may be restarted automatically, if the process size specified in abap/heaplimit was exceeded.
Basic rules: Ensure that the pool is 10 to 15 times as larger as ztta/roll_extension; The exact value is oriented according to the available swap space and the number of users in the host system.
Integration
The swap space must be sized so that it can contain the R/3 Extended Memory and has enough space for the R/3 usage of heap memory (see Swap Space Requirements). There must also be enough space available for competing system users outside of the R/3 System. The swap space must also be large enough to ensure a safety reserve.
Activities
Unit: 1 MB
Default value: 128 MB
Recommended value: 200 to 500 MB, approximately 5 MB for each R/3 user (pay attention to operating system dependencies)
You can find the values from the configuration examples (Contents button). You can find more information on Windows NT under Setting Dimensions for Sufficient Extended Memory.
Changes: Customers can make changes.
