Online Tutorials & Training Materials | STechies.com
Register Login

Profile parameter for export/import buffer instances

|| 0

Profile parameter for export/import buffer instances
Stechies

This note explains the profile parameters for the export/import buffer, for the ESM (export/import-shared-memory) buffer, the OTR (Online Text Repository) buffer and CUA buffer.

The profile parameters for the dimensioning of the following buffers are explained below:

1.  You can use the ABAP command EXPORT TO SHARED BUFFER to save data clusters in a general work process buffer, the export/import buffer (or shared buffer).

Export/import buffer:

        a) Size in the shared memory:
        rsdb/obj/buffersize [in kilobytes]
        Default: 4,096 [kB]
        Maximum: 2,097.148 [kB] for kernel Release 3.I to 6.20 with a patch number lower than 1129. Size restrictions no longer apply to releases above this level.

        b) Number of the objects that can be buffered (directories):
        rsdb/obj/max_objects
        Default: 2.000
        The number of directories must be adjusted to the total size of the buffer: Each directory requires approximately 430 bytes of administrative information in the buffer. All together, the directories should not take up more than 20% of the buffer to allow enough memory space for the objects to be buffered.

                       The following is a rough guideline: The value for rsdb/obj/max_objects should not be greater than half the value of rsdb/obj/buffersize. However, this value may be higher in releases lower than 640, up to the value of rsdb/obj/buffersize also, since a directory requires less memory in these releases.
If an overflow occurs, see Note 373986. If the runtime error EXPORT_BUFFER_NO_MEMORY occurs, see Note 520684.

2. ESM buffer:

As of kernel Release 6.10, you have an additional new ABAP command EXPORT TO SHARED MEMORY, that you can use to save data clusters in the export/import shared memory buffer (or ESM buffer for short).

        a) Size in the shared memory:
        rsdb/esm/buffersize_kb [in kilobytes]
        Default: 4,096 [kB]
        Maximum: 2,097.148 [kB] for kernel Release 3.I to 6.20 with a patch number lower than 1129. Size restrictions no longer apply to releases above this level.

        b) Number of the objects that can be buffered (directories):
        rsdb/esm/max_objects
        Default: 2.000
        The information in point 1b also applies here.

3. OTR buffer:

The online text repository buffer is available as of kernel Release 6.10. Here texts are saved that are used in BSP for example.

        a) Size in the shared memory:
        rsdb/otr/buffersize_kb [in kilobytes]
        Default: 4,096 [kB]
        Maximum: 2,097.148 [kB] for kernel Release 3.I to 6.20 with a patch number lower than 1129. Size restrictions no longer apply to releases above this level.

        b) Number of the objects that can be buffered (directories):
        rsdb/otr/max_objects
        Default: 2.000
        See point 1b.

4. CUA buffer:

The runtime objects of the GUI interface are stored in the CUA buffer. These are saved on the database in the tables D345T, D346T and D342L.

        a) Size in the shared memory:
        rsdb/cua/buffersize [in kilobytes]
        Default: 3,000 [kB]
        Maximum: 2,097.148 [kB] for kernel Release 3.I to 6.20 with a patch number lower than 1129. Size restrictions no longer apply to releases above this level.

        b) The number of directories is calculated from the buffer size and cannot/must not be set explicitly using a profile parameter.


Caution:
Take the following points into consideration if you are increasing the buffer parameters in the SAP profile:

    Your system must have enough main memory. The main memory is limited, especially on 32-bit platforms, so any increase in the buffer must be in line with existing memory management.

    We cannot prescribe definite guide values for optimal buffer sizes. The appropriate sizes depend on the hardware, release level, dataset in the system and applications used.

    You must restart the system for the profile change to take effect.

    Once the adjustment has taken place, we recommend that you use transaction ST02 to check the buffer after a short while.