Symptom
The ABAP program terminates with short dump STORAGE_PARAMETERS_WRONG_SET.
Other Terms
Reason and Prerequisites
The session terminates because the maximum permitted or technically possible amount of memory (or, more exact: address space) has been exceeded.
Quotas are used to terminate sessions with unreasonably high address space and memory requirements in time to prevent other programs or the actual operating system from being negatively affected by resource bottlenecks.
If the error mentioned above occurred, you must determine if the terminated session exceeded a reasonable size, if the operating system limits or quotas have been exceeded, or whether higher quotas can be set.
The following explains how to determine the size of a session:
SM04-> Memory: Total size of all sessions within a log on, and sizes of the individual subsessions
- On 64-bit platforms, the address space that can technically be used is sufficient. This termination usually occurs if operating system quotas or SAP system quotas have been exceeded.
- On 32-bit platforms, the maximum address space that is technically possible is severely restricted. Here, the termination usually occurs because the technical limits of the operating system, which are usually below set quotas, have been exceeded The maximum address space available to an ABAP session is limited to a few 100 MB in the standard setting. Under certain circumstances, the space can be increased by a few 100 MB using special parameter settings; however, this will affect buffer sizes and therefore performance negatively.
Quotas are used to terminate sessions with unreasonably high address space and memory requirements in time to prevent other programs or the actual operating system from being negatively affected by resource bottlenecks.
If the error mentioned above occurred, you must determine if the terminated session exceeded a reasonable size, if the operating system limits or quotas have been exceeded, or whether higher quotas can be set.
The following explains how to determine the size of a session:
- While the session is active:
SM04-> Memory: Total size of all sessions within a log on, and sizes of the individual subsessions
- After the session ended:
