cancel
Showing results for 
Search instead for 
Did you mean: 

Memory is low : Leave the transaction before taking a break

Former Member
0 Kudos

Hi,

In our GTS 7.2 system we are getting the message " Memory is low : Leave the transaction before taking a break".

We able to get the results , still getting these messages.

I checked the forums and snotes and increased the Extended memory still same message.

We are on 64 bit with Windows server.

Please suggest what are the things i need to check to fix this message.

Thanks,

Subhash.G

Accepted Solutions (0)

Answers (6)

Answers (6)

khampariamukesh
Active Participant
0 Kudos

Hi Subhash,

This issue generally occurs when user is trying to utilised the more memory allocataed to work process...

Once it cross the limit of Heap Memory, your request will be canclled with such message.

You can do following

     1. Retrieve the data in small bunch.

     2. Trigger the report and check in SM04 and see the Memory utilization of WP associated with report.

          if this reaches to high limit of Heap memory then you will surely receive such message.

          Then we can plann to increase of Heap memory as well (if option 1 is not good for you).

1st option is always recommended. 2nd is rarely recommended because we should not perform change in memory just because of one user is facing issue.

Thanks

Mukesh

Former Member
0 Kudos

Hi,

     please i need to know all reasons that causes this Message (memory low. leave the transaction before taking a break )

Thanks.

former_member184455
Active Participant
0 Kudos

Hi Mohamed,

The message is caused by an user with high amount of allocated ABAP memory.

Take a look into SM04 or STAD to see how much it is.

With help of Debugger (http://scn.sap.com/people/stephen.pfeiffer/blog/2011/03/24/new-memory-analysis-features-in-netweaver...) or Memory Inspector (SMI) analyze which objects are feeding up the memory.

Best Regards,

Randolf

Former Member
0 Kudos

Hi Gurus

I get an error similar to the one discussed above, but me I get as per the below dump.

Runtime Error          CONNE_IMPORT_WRONG_COMP_LENG

Exception              CX_SY_IMPORT_MISMATCH_ERROR

       Occurred on     05.03.2013 at   17:00:14

Error when attempting to IMPORT object "AEND".

What happened?

Error in ABAP application program.

The current ABAP program "ZHPWHOTC" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',

was neither

caught nor passed along using a RAISING clause, in the procedure "IMPORT_TE"

"(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

When importing the object "AEND", the component 4 in the dataset

had a different length from the corresponding component of the

target object in the program "ZHPWHOTC".

The length is 8 in the dataset, but 40 in the program.

------------------------------------------------------------------------

           Last error logged in SAP kernel

------------------------------------------------------------------------

Former Member
0 Kudos
former_member189546
Active Contributor
0 Kudos

Hello,

As stated in the note #116042, the message "memory low leave

transaction before taking a break." is informational and

not an error but in this case it appears to indicate that processes

are going into heap too early as EM is exhausted.

For Windowws check note 88416 phys_memsize is important parameter

regards,

John Feely

Former Member
0 Kudos

Hi all,

Up on digging in to the issue, i have noticed roll_extension is the parameter behind the message.

The task is taking 4 gb of extended memory and going to heap after that, i have increased the roll extension and successfully avoided the message.

Thanks,

Subhash.G

former_member189546
Active Contributor
0 Kudos

Hello,

Please check memory parameters with note 88416

Are you getting memory dumps in ST22?

regards,

John Feely

Former Member
0 Kudos

Hi,

I have not found any st22 dumps or sm21 log for this, output is coming and the warning on the toolbar showing "Memory is low".

em/address_space_MB = 8192

em/initial_size_MB =18000

em/global_area_MB =4096

abap/heap_area_dia = 6 gb

abap/heap_area_total = 36 gb

rdisp/ROLL_SHM & PG_ SHM = 65536

There was a swap space of 23 gb on the system with 16 gb ram.

Thanks,

Subhash.G