cancel
Showing results for 
Search instead for 
Did you mean: 

ECC6.0 EHP4 IDES-work process restarted,session terminated error while MIRO

0 Kudos

Hello colleagues,

I am facing a "Work process restarted, session terminated error while tring to use the transaction MIRO in the system. I tried the following fixes as suggested in some previous posts on this issue.

1) Adding profile parameters abap/heaplimit, ztta/roll_area, ztta/short_area to the instance profile.

2) Upgrading the kernel.

Still the issue persists.

Please give some suggestions to tackle this issue.

Thanks and regards,

Sudarsan.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Siva,

I couldn't find any files with these names or similar names.

Thanks and regards,

Sudarsan.

sivakumar_kilari3
Active Contributor
0 Kudos

ztta/diag_area = 350000

The maximum value recommended as a workaround is 530000 bytes

Note 1257931 - Screen output problems for transactions with large screens

https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=1257931

sivakumar_kilari3
Active Contributor
0 Kudos

ztta/diag_area = 350000

The maximum value recommended as a workaround is 530000 bytes

Note 1257931 - Screen output problems for transactions with large screens

[https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=1257931]

0 Kudos

Hi Siva,

The issue got solved by setting this paramater to 400000. Thank you very much for the solution.

Thanks and regards,

Sudarsan.

Edited by: Sudarsan C Narayanaswamy on Jun 10, 2011 3:54 AM

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Just need to confirm if you have restarted the SAP System after making changes in the instance profile, so that the changes gets reflected. Also please check the allocation of Virtual memory and RAM availability for your SAP Server.

Thanks

Rattandeep Singh

0 Kudos

Hi Rattan,

Yes. I restarted the SAP system after updating the profile.

Thanks and regards,

Sudarsan.

0 Kudos

Hello colleagues,

I can also see a SYSTEM_CORE_DUMPED error in ST22. The details are as follows,

Termination occurred in the ABAP program "SAPLMR1M" - in "SYSTEM-EXIT".

The main program was "SAPLMR1M ".

In the source code you have the termination point in line 0

of the (Include) program "########################################".

-


Main memory destroyed

-


-


The error occurred because of a main memory overwrite. There may

be an internal error in the R/3 System.

The amount of memory occupied at the time of the termination was:

-


> Roll area......................... 16192 bytes

> Extended memory area (EM)......... 16759360 bytes

> Fixed area........................ 0 bytes

> Short area........................ " " bytes

In the work directory of the SAP system (e.g. /usr/sap/C11/D00/work ),

there may be files called 'mm.dump' and 'mm.info'.

Save these files under other names.

Regards,

Sudarsan

sivakumar_kilari3
Active Contributor
0 Kudos

> In the work directory of the SAP system (e.g. /usr/sap/C11/D00/work ),

> there may be files called 'mm.dump' and 'mm.info'.

> Save these files under other names.

Thanks

Siva

0 Kudos

Hi Siva,

I went through the log files. But couldn't make an inference from the log. Here is last part of the log.

Thu Jun 09 09:53:54 2011

dbmyclu : info : my major identification is 172229638, minor one 0.

dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.

dbmyclu : info : my initial uuid is E0926D9CDA53E4F1A942D48564CC7B08.

dbmyclu : info : current optimistic cluster level: 3

dbmyclu : info : pessimistic reads set to 2.

Thu Jun 09 09:54:44 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Thu Jun 09 09:55:07 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Thu Jun 09 09:55:16 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Thu Jun 09 09:55:40 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Thu Jun 09 09:55:47 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Thu Jun 09 09:55:49 2011

found spool memory service RSPO-ACTIONS at 00000000319CA300

Thu Jun 09 09:55:53 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Thu Jun 09 09:56:07 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Thu Jun 09 09:56:16 2011

      • ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

Can you analyse something from these messges ?

Thanks and regards,

Sudarsan.

sivakumar_kilari3
Active Contributor
0 Kudos

Hi,

Can you check in txn. code ST11 at the most recently changed work process traces (dev_w*) to double click the log file and find out the problem.

Thanks

Siva