Skip to Content
author's profile photo Former Member
0
Former Member

SUM upgrade phase Execution at step: ABAP: Phase MAIN_NEWBAS/XPRAS_AIMMRG is running too long

Posted on May 18, 2015 at 04:02 PM 355 Views

hi Experts,

We are upgrading our solution manager 7.1 SP11 to SP13 through Software Update Manager [SUM] SP13 on windows environment.

but from almost 30 hours i was stuck at this very step: " ABAP: Phase MAIN_NEWBAS/XPRAS_AIMMRG is running ... "

Java installation is completed successful. I dont see any dumps in shadow systems. in SM66 i see one background job running from 30 hours.and in SM37 i see the job RDDEXECL active from the same time stamp.

please advice we are in serious concern about this.

thanks,

Raja

the following 2 images are SM37 job and its job log

sum1.PNG (22.1 kB)
sum2.PNG (24.9 kB)
sum3.PNG (6.3 kB)
sum4.PNG (20.3 kB)
sum5.PNG (13.6 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 19, 2015 at 05:09 PM
    4

    thanks everyone for their help, it really did help me to solve it.

    This is how i finally solved it...

    My Issue:

    "

    2EETW000 sql error: 1205 Transaction (Process ID 117) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    2EETW125 SQL error "1205" during "1205" access: "Transaction (Process ID 117) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."

    1 ETP111 exit code : "12"

    Found this in XPRASUPG.ELG log.

    in SM37 the job that is keep on running for last 2 days in active state "RDDEXECL "

    so even though log says there is an error due to dead lock, it never showed up..as the job RDDEXECL keep on running.

    we have 3 approaches here

    1. restart SUM

    2. Restart shadow instance

    3. restart the job " RDDEXECL"

    i have choosed option 3 as im little worried to try other 2 options as im in middle of execution phase.if it hadnt worked i would have to go through the restart of SUM/Shadow instance.

    thanks,

    Raja

    Add a comment
    10|10000 characters needed characters exceeded

    • Julia Bayrhammer Former Member
      Aug 15, 2016 at 05:01 AM

      Hello,

      I repeat my post from above:

      we are at same point.

      I read note 1947874 and checked job status in SM37.

      After that all RDDEXECL jobs were shown as finished.

      I can't login into shadow instance. So I had a look into via dpmon pf=Instance.

      There I can see, that all dialog workprocesses are in use. Thats the cause why I can't login.

      But tables are not changing, instance seems blocked.

      Is it an option to restart shadow instance now? Or where can I see, what's the problem?

      Regards,

      Julia

    Comment on This Answer
  • author's profile photo Former Member
    Former Member
    Posted on May 18, 2015 at 04:53 PM
    2

    Hi Raja,

    As you are performing Solman 7.1 SP11 to SP13 upgrade and step "MAIN_NEWBAS/XPRAS_AIMMRG" should not take more than 2 hrs to complete;

    So there might be chances of deadlock occurrence. Please check the same in DB01. also please check upgrade logs in <drive>:\usr\sap\SUM\abap\log provide the screenshot of logs.

    Thanks.

    Regards,

    Jaskirat Singh

    Add a comment
    10|10000 characters needed characters exceeded

    • Julia Bayrhammer Former Member
      Aug 11, 2016 at 02:26 PM

      Hello,

      we are at same point.

      I read note 1947874 and checked job status in SM37.

      After that all RDDEXECL jobs were shown as finished.

      I can't login into shadow instance. So I had a look into via dpmon pf=Instance.

      There I can see, that all dialog workprocesses are in use. Thats the cause why I can't login.

      But tables are not changing, instance seems blocked.

      Is it an option to restart shadow instance now? Or where can I see, what's the problem?

      Regards,

      Julia

    Comment on This Answer
  • author's profile photo Manu Mohandas
    Manu Mohandas
    Posted on May 18, 2015 at 04:07 PM
    1

    Hi Raja ,

    This phase generally takes a long time to complete . If the Job is active [ Check in sm66 , sm50 , etc ] and updating there is nothing to worry .

    The following Note should help you


    1947874 - Performance analysis for XPRAS_AIMMRG phase


    Troubleshoot as recommended in the Note


    Thanks ,

    Manu

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      May 18, 2015 at 04:20 PM

      thank u Manu for the quick response.

      in sm 50 i see the job is on hold but in sm 37 it is active..

      and how to check if it is updating anything in the system? i dont see any logs in the backend systems after the job started in May 17, 5:24 AM MST.

      sum6.PNG (44.9 kB)
  • author's profile photo Manu Mohandas
    Manu Mohandas
    Posted on May 18, 2015 at 04:30 PM
    1

    Hi Raja ,

    If the status of the process does not change for a long time in SM50 then more probable that the work process is stalled .

    You may also take a trace using ST12 , ST05 . Check for any DB deadlocks or long held locks .

    Is there any CPU / Memory contention ?

    Believe you could wait for some more time , in the meantime take a trace or check in STAD

    Thanks ,

    Manu

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Ashutosh Chaturvedi
    Ashutosh Chaturvedi
    Posted on May 18, 2015 at 04:51 PM
    1

    Hi Raja,

    - Are you getting any dump related to this in ST22?

    - Check the status of the job RDDEXECL

    run the transaction sm37 and job->check.

    - Attached the logs for the phase and also the job log.

    With Regards

    Ashutosh Chaturvedi

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.