cancel
Showing results for 
Search instead for 
Did you mean: 

XPRAS SHD AIMMERGE - EMADM Owner=5 Deadlock ?

joo_migueldimas
Active Participant
0 Kudos

Hello,

System: Solution Manager 7.1

Type: Distributed System

Operation System: Win Server 2008 (R2)

Database: MS SQL Server 2008 (R2)

I´m doing the support packages update for Solution Manager 7.1 to the Stack 05, for this I´m using the SUM tool (latest version). The phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/XPRAS_SHD_AIMMERGE is running for many hours... it doesn't pass this phase! I checked some log files of shadow instance.

Can you help me how to solve this problem?

______

dev_w0

______

I Fri Oct 05 15:30:33 2012

I  *** WARNING =>  MtxLock 00000000150F19E8    EMADM owner=5 deadlock ? [mtxxx.c      2570]

I  

I Fri Oct 05 15:31:33 2012

I  *** WARNING =>  MtxLock 00000000150F19E8    EMADM owner=5 deadlock ? [mtxxx.c      2570]

I  

I Fri Oct 05 15:32:33 2012

I  *** WARNING =>  MtxLock 00000000150F19E8    EMADM owner=5 deadlock ? [mtxxx.c      2570]

I  

I Fri Oct 05 15:33:34 2012

I  *** WARNING =>  MtxLock 00000000150F19E8    EMADM owner=5 deadlock ? [mtxxx.c      2570]

_______

dev_disp

_______

Fri Oct 05 15:12:06 2012

*** ERROR => DpHdlDeadWp: W13 (pid 9352) died (severity=0, status=0) [dpxxwp.c     1706]

Fri Oct 05 15:17:05 2012

*** ERROR => DpHdlDeadWp: W13 (pid 8536) died (severity=0, status=0) [dpxxwp.c     1706]

Fri Oct 05 15:17:25 2012

***LOG Q0J=> DpEnvCheck, no_wp () [dpxxdisp.c   8423]

***LOG Q0G=> DpRqBadHandle, bad_req ( SPO) [dpxxdisp.c   6111]

*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: senseless request (line 8425): [dpxxdisp.c   6113]

-IN-- sender_id DISPATCHER        tid  -1    wp_ca_blk   -1      wp_id -1

-IN-- action    SEND_TO_WP        uid  -1    appc_ca_blk -1      type  SPO  

-IN-- new_stat  NO_CHANGE         mode 255   len         0       rq_id 6744

-IN-- req_info  SET_SYSTEM_USER,DP_SPOOL_ALRM

-IN-- msg_name  -                   

Fri Oct 05 15:22:05 2012

*** ERROR => DpHdlDeadWp: W13 (pid 10460) died (severity=0, status=0) [dpxxwp.c     1706]

Fri Oct 05 15:22:25 2012

***LOG Q0J=> DpEnvCheck, no_wp () [dpxxdisp.c   8423]

***LOG Q0G=> DpRqBadHandle, bad_req ( SPO) [dpxxdisp.c   6111]

*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: senseless request (line 8425): [dpxxdisp.c   6113]

-IN-- sender_id DISPATCHER        tid  -1    wp_ca_blk   -1      wp_id -1

-IN-- action    SEND_TO_WP        uid  -1    appc_ca_blk -1      type  SPO  

-IN-- new_stat  NO_CHANGE         mode 255   len         0       rq_id 6745

-IN-- req_info  SET_SYSTEM_USER,DP_SPOOL_ALRM

-IN-- msg_name  -                   

I found the following note - 1309072 - System standstill: MtxLock EMADM ...but I don´t quite understand the solution mentioned, even if this is my main problem here!

Can you help me please!?

Any tip?

Accepted Solutions (1)

Accepted Solutions (1)

joo_migueldimas
Active Participant
0 Kudos

Hello,

The problem was solved... what I did was, first I stopped all sap instances, the central instance and the shadow instance, then I gave more paging file space (swap space) to the windows operation system, I rebooted the server and after this I started both sap instances and I ran the SUM tool without any problem, this problem no more longer appeared.

Kind regards,

JD

Answers (0)