Background running for long time

[former_member203165]

Hi,

One background job is running for along time(since 48hrs),

i have checked in the sm50 the job is running state but in the action column it is blank means it is not showing any of the states roll in/roll out /Sequential read/Physical read/insert/update/delete.

Please suggest how to analyze these job.

Thank in advance...........

Regards,

Chandrashekar.

[former_member183069 · Accepted solution]

Hi Chandrashekar,

In SM37 give the job name and check it and u can see if any log there.

Regards,

K. Kartthikeyan

[former_member203165 · Accepted solution]

Hi Kartthikeyan,

Now the job is finished after 49 hours without errors.

Thanks& Regards,

Chandra

[adam_krawczyk1]

Hi Chandrashekar,

I found this thread not answered yet. The easiest way to see what is going on in long running program is to run SAT / SE30 transaction and measure at least some minutes of it to see what takes most time (wrong algoritym, not optimized internal tables processing or database access without indexes etc.). SAT transaction allows to run measurements also for another user or background task which makes it powerful tool.

Here is the link to similar topic:

http://scn.sap.com/thread/3309655

Regards,

Adam

[xymanuel]

Hi Kumar,

if you have the authorization,

go to Transaction "SAT", and attach online to the running process (parallel mode) for about 1min.

Analyse where the time is spent.

Another way, if you have ABAP experiance:

Go to SM66.

Double click on the long running Backgroundprocess.

Press "Debugging".

A new debuggerwindow will open, and the process is suspended in the debugger.

Analyse the internal tables, and make a few steps with the debugger.

If you dont want to kill the process afterwards, just leave the debugger.

The process will continue normal without breaking.

Regards

Manuel