Report Error (Basis)

Question

Hi Experts,
I developed a report which involves alot of calculations,When i executed that report on Cal Year/Mon it shows results but when i drill down it by day r department,It shows following error and disconnects
<b><i>1)Error An exception with the type CX_SY_EXPORT_NO_SHARED_MEMORY occured
An exception with the type CX_SY_EXPORT_SHARED_MEMORY occured.But was neither handled,nor declared in a RAISING.
2)Message no.RS_EXCEPTION000
Error No space left in shared memory</i></b>
How to resolve it and what are the consequences on system if we increase shared memory
Thanks

Answer 1

Hi,
Profile parameter for export/import buffer instances  
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.
Other terms
shared buffer, maximum buffer size
Reason and Prerequisites
The profile parameters for dimensioning the following buffers are explained below:
1. Export/import buffer:
You can use the ABAP commands EXPORT TO SHARED BUFFER to save data clusters in a general work process buffer, the export/import buffer (or shared buffer).
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).
3. OTR buffer:
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.
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.
Solution
1. 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. Every directory requires approx.
b) Number of the bufferable objects (directories):
rsdb/obj/max_objects
Default: 2.000
The number of directories must be adapted to the total size of the buffer: Each directory needs approximately 430 bytes of administrative information in the buffer. All together, the directories should not take up more than 10% of the buffer, to allow enough memory space for the objects being buffered.
                        The following applies as a rough guideline: The value of rsdb/obj/max_objects shold not be larger than one quarter of the value of rsdb/obj/buffersize.
If an overflow occurs, refer to Note 373986. If you get the runtime error EXPORT_BUFFER_NO_MEMORY, see note 520684.
1. ESM buffer:
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. Every directory requires approx.
b) Number of the bufferable objects (directories):
rsdb/esm/max_objects
Default: 2.000
The information in point 1b also applies here.
2. OTR buffer:
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. Every directory requires approx.
b) Number of the bufferable objects (directories):
rsdb/otr/max_objects
Default: 2.000
See point 1b.
3. CUA buffer:
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. Every directory requires approx.
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 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 version, 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 check the buffer after a short while using transaction ST02.
/manfred