Skip to Content
avatar image
Former Member

scheduled jobs stuck after a certain time

We are using SAP MII 12.2 SP6 Patch 5 (20.12.2013).

We have many scheduled jobs with different time periods.

Most jobs are scheduled with a period of 10 or 20 seconds.

Our problem is that the jobs will run for a certain time (can be 2 hours, but as well 2 days) properly, but suddenly single jobs stuck and  we have to disable/enable the job to resume in running status.

SAP proposed to use latest MII release. First we used SAP MII 12.1 SP5 Patch 3. But the release upgrade to SAP MII 12.2 SP6 Patch 5 did not improve the situation!

 

Do you have any idea how to get rid of this problem?

Please provide your suggestions.

Thanks & Regards,

Michael

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jan 30, 2014 at 01:00 PM

    Hi Michael,

    I read about a similar issue in the Administrative Handbook of MII.

    Have a look at page 9.

    http://wiki.scn.sap.com/wiki/download/attachments/15603/SAP%20MII%20Handbook.pdf?version=2&modificationDate=134694570100…

    In this page there is mention of an issue where asynchronous transactions get stuck.

    Also there a not is mentioned for the resolution of the problem.

    Note No: 1959717

    You could also check this thread:

    Regards,

    Rohit Negi.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Stefanie,

      As mentioned by you, there are lot of jobs running.

      So I can say you may also have to check on many other possibility,

      1. If there is many jobs using same resource in parallel, In that case one job waiting for other job to complete.

      2. Also what is the time duration of each job. Whether your transaction is able to finish that job within that time frame. If not this may put the other jobs on wait and may go to next schedule and you can see lot of delay.

      3. Database size has become very high so any insert or update or select operation may be taking more time.

      4. In any RFC interface jobs check whether you are taking status back to MII after the successful execution of RFC.

      You can make use of sm50 Tcode to see the running jobs in ERP, so that you can analyse what time it is taking.

      I suggest to raise an OSS ticket so that you can get quick fix.

      Thanks,

      Padma Rao

  • Feb 01, 2014 at 02:21 AM

    Hi,

    Take a look at Memory consumption angle , if any node is eating memory more than usual and you may also need to look at associated hardware upgrade accordingly.

    Nikhil

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 03, 2014 at 06:35 AM

    Hi Michael,

    Sometimes these kind of issue's arise due to DB dump.. do have a re look at interactions to DB side.. you may get your answer analyzing it ...

    Thanks

    Ruchir

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 06, 2014 at 08:06 AM

    Hi Michael,

    We have faced this issue, the solution can be to reset the indexes at your DB; as your scheduled jobs are running is small intervals. This makes the performance of DB slow which in turn results scheduled jobs to get stuck.

    Resetting your indexes at the DB level will improve your application's performance considerably. Preferably, indexes should be reset quite often in your case to ensure your jobs are not stuck.

    Regards

    R

    Add comment
    10|10000 characters needed characters exceeded