Database updates taking a long time, how to debug

[Former Member]

I am working on an issue where the DB update tasks run for long time keeping the objects locked. How do I debug this to find where the time is being consumed.

[Former Member]

hi Lal ,

what Transaction u are running ? check SM50.

Regards

Prabhu

[Former Member]

Hi Prabhu,

Thanks for the quick reply.

To give a brief, I am using the transaction VL02n(outbound delivery) , changing and then saving it. I see the message 'Delivery saved', but in SM12/13 I see the locks held until the update tasks run. These tasks take long. In SM50 I can see the program name which is a include with many functions. How can I do a step-step debugging.

Thanks

Anupama

[Former Member]

Hi,

Update Task is derived from SAP LUW's, which all updates come under FM Updates, untill all those are done, the lock(Enqueue) is not release, For Step-by-Step debugging, goto the main program, look for the subroutines, the design of SAP programs are simplified using these subroutines or you can get the include files, where you can put breakpoints and run the transaction, so that you will be debugging in places where you want to what is happening.

Cheers...

Santosh.

[Former Member]

SE30 runtime analysis will give you a breakup of time being consumed.

[PS_1978]

Hi Anupama,

U can check it either by using SE30 (Runtime Analysis) or ST05 (SQL Trace).

Regards,

Phani.

Message was edited by:

Sivapuram Phani Kumar

[Former Member]

Hi Lal ,

To give a brief, I am using the transaction VL02n(outbound delivery) , changing and then saving it. I see the message 'Delivery saved',

but in SM12/13 I see the locks held until the update tasks run.-->

<b> Yeah , this is std.SAP while doing the changes in any object SAP will lock that Object. </b>

These tasks take long--> <b>It may be depends upon ur system performance</b>

.

In SM50 I can see the program name which is a include with many functions. How can I do a step-step debugging-->

<b>rin ST05 to find out which step is taking long time</b>

<b>

Have u done any changes in std.SAP programs ?

2.Are u activating any Z tables within this Transaction ?

3.Have u activated any User Exits ?

4.Any Support Packages Upgrades?

Regards

Prabhu

</b>

[Former Member]

you can switch into debug before clicking SAVE in your delivery (use /h in command window), then you can enable update debugging "Settings -> Update debugging"

Then SAP will stop in update task and there you can debug all FMs which are called in update task.

I would start from SM50 though to determine which program takes the most time, then set breakpoint in that program and debug it if necessary using update debugging described above.