SYSTEM_IMODE_TOO_LARGE

[Former Member]

Dear all,

I am getting an DUMP " SYSTEM_IMODE_TOO_LARGE"

CAN ANYBODY SUGGEST HOW CAN I overcome this dump...

Regards,

Neeraj

[Former Member]

Hi Neeraj,

Welcome to SDN.

Please check this SAP OSS Note 548845 and perhpas you may want to forward this to BASIS for advise/help.

Symptom

A SYSTEM_IMODE_TOO_LARGE runtime error occurs.

Other terms

64-bit, SAP kernel, memory consumption

Reason and Prerequisites

The runtime error "SYSTEM_IMODE_TOO_LARGE" is triggered if a user context or, more specifically, an internal session tries to use more than 2 GB of main memory. The restriction to 2 GB stems from the fact that signed 32-bit variables were frequently used. With unsigned 32-bit variables, memory sizes may be as much as 4 GB.

Solution

As of SAP_BASIS 6.20 Support Package 38, internal sessions can be larger than 2 GB and even larger than 4 GB on 64-bit hardware. In addition, the buffers for database tables and some other buffers can also be set larger than 2 GB and 4 GB, respectively. The Support Package has been available since the end of March 2004. The Support Package requires the 6.20 Kernel Patch Level 1269 or higher. Runtime error SYSTEM_IMODE_TOO_LARGE then no longer occurs. As of SAP_BASIS 6.40, the function is included without any additional Support Packages. For Releases 4.6B to 6.10, such a patch cannot be made available so the restriction to 2 GB still applies.

We therefore recommend that you consider the following if the "SYSTEM_IMODE_TOO_LARGE" runtime error occurs:

Are you using the application as intended? For example, a memory bottleneck may occur if you select too much data.

Does the memory consumption of the application depend on Customizing parameters whose settings may be inadequate?

Is the application program economical in its use of memory? For example, you must explicitly delete the contents of an internal table (FREE statement) before you can reuse the memory. This is significant, particularly if transactions are running for a long time. Furthermore, you can only use the garbage collector to release objects (class instances) and dynamically generated data objects if they can no longer be accessed using references; you must delete the corresponding reference variables. To examine this question, create a problem message under the component responsible for the application program, if you have not already done so.

The "Memory Inspector" is a tool that may be used to analyze the memory consumption of ABAP programs. This tool is available with SAP_BASIS 6.40 and with SAP_BASIS 6.20 Support Package 29. Among other things, the "Memory Inspector" displays ranked lists of large internal tables, strings and dynamically generated (data) objects. Furthermore, the tool displays dependencies between individual objects; this permits an analysis as to why certain objects cannot be released by the garbage collector. For information about analyzing the memory consumption (also for earlier releases), see Note 649327.

For Releases 4.6B to 6.10, you can use a profile parameter that is not globally released to increase the maximum size of an internal session from 2 GB to 4 GB. However, most monitoring tools are unable to correctly display values over 2 GB; this applies to Transactions sm04, sm50, st02, st03, se30, the memory consumption display in the debugger, some outputs in trace files and some other locations within the system. SAP can therefore only provide limited support for any internal sessions over 2 GB. If customers increase the maximum size of an internal session from 2 GB to 4 GB, they do so at their own risk. SAP shall not be held responsible for errors caused by internal modes over 2 GB. We cannot guarantee that no other errors than those mentioned here will occur. The problem that occurs in both the 32-bit Kernel and the IBM iSeries if an internal session consumes more than 3.4GB is solved as of the Patch delivered in Note 833336. At present, however, we are not aware of any other errors that would seriously impair productive use of the application. We can provide the name of the profile parameter as well as information regarding the use of the profile parameter on request. For this, create a problem message with the BC-ABA-LA component. As of SAP_BASIS 6.20 Support Package 38 and SAP_BASIS 6.40, the profile parameter is no longer required and should be deleted from the profile, otherwise there is an upper limit of 4 GB.

The "SYSTEM_IMODE_TOO_LARGE" runtime error occurs regardless of the operating system platform and configuration of the memory areas. In particular, you cannot avoid this error by changing memory profile parameters such as ztta/roll_extension and abap/heap_area_nodia.

In Releases 4.6B to 6.10, 64-bit hardware is utilized in such a way that an application server can have a larger number of user contexts at the same time. In addition, various buffers (for instance program buffers, buffer for database tables) may now be up to 2 GB each.

The restriction of internal sessions to 2 GB was introduced when the aforementioned problems occurred; the restriction exists since the 4.6D Kernel Patch 1286 and the 6.20 Kernel Patch 368.

Hope this will help.

thanks

karthik

reward me points if usefull