Skip to Content
-1

Long running job in S/4 Hana migrated system

Hi

There are a few data intensive jobs which ran for 30 minutes on a traditional database is now running for more than +9 hours in HANA Database 1605. The programs are both ATC check cleared. Is there any specific process that need to follow. AMDP usage is also not helping out the cause.

Is it a basis related issue, work process error something. How will I be sure?

Do we need to run a specific index generating job upon migration to HANA Database?

Regards

Diganto

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Jun 29, 2017 at 07:06 AM

    Passing ATC check does not guarantee that a program is well written. That is why peer review of source code by another programmer is a good thing.

    When we upgraded out BW system to HANA, we found many places with less than optimal coding (in the area of selects), where you get away with in Oracle (it's not as fast as it could be, but the overall runtime is ok), that cause huge issues in HANA.

    You need to run performance traces on the jobs and find out where the database queries are taking a long time. Then fix them. Typically, numerous select singles (even keyed fully!), FOR ALL ENTRIES selects instead of INNER JOINS. There is an OSS note concerning FOR ALL ENTRIES, and a way of adding hints to the SELECT to improve performance where you have to have them.

    Add comment
    10|10000 characters needed characters exceeded

    • Just AMDP push down were worked out at the data intensive parts of the code. From 72k, the program has run down to 7600 seconds.

      Further push down is under way.

      Thanks for helpful inputs.

      Regards

      Diganto

  • avatar image
    Former Member
    Jun 28, 2017 at 12:16 PM

    Hi Diganto,

    The problem that you described, can have the root cause from several layers of the newly installed HANA system(1605). Implementation of AMDP does not necessarily optimizes the performance each time. It is encouraged, when you have a large retrieval:filter ratio + few database intrinsic operations , which otherwise would have to be done via iteration, imperative logic, etc etc..

    At this moment of time, you can take the ABAP trace and SQLM trace and get the idea about the internal processing.

    Cheers,

    Shubhamoy

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Diganto,

      You are right, it is quite expected that jobs running in Oracle should run faster on HANA. But, After migrating to HANA and optimizing the programs to extract the benefits that HANA provides, requires some specific ABAP workout + Basis workout. Without the ABAP workout you cannot bet that it would run faster in HANA. There are several parameters that are considered for that faster running.

      From the ABAP prespective, I can say that, the jobs that are talking too long to finish in S/4 , you can trace that out. If you find any glitch, you can then move ahead with ABAP on HANA - Consulting.

      For your specific question on work process lock, I believe you can check with an BASIS guy/ or you might want to post your query in BASIS community, if there is any :)

      Also, Please have look at the below docs :

      https://www.sap.com/documents/2015/07/9c5c8fbd-5b7c-0010-82c7-eda71af511fa.html#

      https://blogs.sap.com/2016/02/08/migration-to-sap-hana-best-practices/

      Cheers