Scribd
Upload
444 views2 pages

Sapnote 0000116042 Memory Low

This SAP note discusses a "Memory low" message that may appear in transactions. The message does not indicate an error, but rather that extended memory is getting low. It advises users to continue working normally but exit transactions before long breaks. System administrators should check for high usage of extended memory or many work processes in a "PRIV" state, which could indicate a memory configuration problem. If extended memory usage is over 90% or many processes are in PRIV state, the memory configuration may need to be increased.

Uploaded by

Siva Ram Prasad
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
444 views2 pages

Sapnote 0000116042 Memory Low

This SAP note discusses a "Memory low" message that may appear in transactions. The message does not indicate an error, but rather that extended memory is getting low. It advises users to continue working normally but exit transactions before long breaks. System administrators should check for high usage of extended memory or many work processes in a "PRIV" state, which could indicate a memory configuration problem. If extended memory usage is over 90% or many processes are in PRIV state, the memory configuration may need to be increased.

Uploaded by

Siva Ram Prasad
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SAP Note 116042 Note Language: English

Message "Memory low."


Version: 1 Validity:
Valid Since 23.08.2001

Summary
Symptom
In any transaction, the following message is generated at the bottom of the screen 00072 "Memory low. Leave the transaction before taking a break!"). User and system adminstrators do not know how they should respond to this message.

Additional key words


Message 00072, extended memory, heap memory, PRIV, PRIV mode

Cause and prerequisites


This message is NO error message. In certain cases, it may point to a performance problem. The information "Memory low" only refers to ONE memory area of the R/3 System, the extended memory. However, the users can request aditional memory in a different memory area, the heap memory, and can continue to work normally. However, a work process is reserved exclusively for the users who use heap memory for that time (that is known as PRIV mode). In certain configurations and systems, the use of heap memory is even intended! The described message is new in Release 4.0 (only the message, the described situation has also already occurred in Release 3). This may be the reason that many users and administrators complain about the "memory errors" and "memory problems" after upgrading to Release 4.0 although objectively no errors can be found.

Solution
What should users and system adminstrators do when they receive this message. User: ----------------------------------------------------------------------Users should proceed as proposed in the long text to the message: "Continue to work as normal and exit the transaction before you take a long break." System administrators: ----------------------------------------------------------------------Under certain circumstances the message may point to a performance bottleneck. Therefore system adminstrators should check the following if users report that this message occurred:

1.

Call the work process overview (Transaction SM50) and observe this some minutes (pushbutton -> Refresh) - see, whether work processes remain in the state Status = stopped and Reason = PRIV, Status = running and Action = roll in
Page 1 of 2

21.11.2011

SAP Note 116042 -

Message "Memory low."

Status = running and Action = roll out If you find more than 50% of the work processes in this status, then there may be a problem in the configuration. If you find less than 50% of the work processes in this status, no problem exists.

2.

Call Transaction ST02. Check the field "Extended memory" in section "SAP memory", "Current use %". This indicates the current consumption of extended memory. If this value is > 90%, a problem may exist in memory configuration. If this value is < 90% is, no problem exists.

What needs to be done? If you find that extended memory is configured too small, then you should increase it. It may also be necessary to increase the number of work processes.

Header Data
Release Status: Released on: Master Language: Priority: Category: Primary Component: Secondary Components: BC-CST Client/Server Technology Released for Customer 02.09.1998 22:00:00 German Recommendations/additional info Performance BC-CCM-MON-TUN Performance Monitors (TCC)

Valid Releases
Software Component SAP_APPL SAP_APPL SAP_APPL Release 40 45 46 From Release 40A 45A 46A To Release 40B 45B 46B and Subsequent X X X

21.11.2011

Page 2 of

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy