Workflows stopping due to deadlock on INDX

[Michael Pokraka]

Hi Phil,
There are a couple of notes relating to deadlocks on OSS. Also search for 'performance' for some other related useful notes.
 
I've also got a problem with workflwos 'stuck between steps' and have been unsuccessful in restarting them, you might have more luck than I did with SWPC. Or you may be able to restart the transaction in SM58.
 
Cheers
Mike
 
On Mon, Jun 23, 2003 at 09:07:32AM +0100, Watkins, Philip wrote:
> Sergey
>    We have that job running and they have not restarted. The problem is that
> the last step showing in the log has completed with no errors, the next step
> just did not get started. Restarting workflows with errors does not pick up
> this process.
>
>           Phil
>
> -----Original Message-----
>> From: Breslavets, Sergey [mailto:Sergey.Breslavets at anheuser-busch.com]
> Sent: Friday, June 20, 2003 6:37 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflows stopping due to deadlock on INDX
>
>
> Hi Phil,
> they are probably in "Temporary Error" status and should be restarted by
> SWWERRE
> job - check SWWWIRET-Errortype for the workitem.
>
> regards,
> Sergey
>
>
> -----Original Message-----
>> From: Watkins, Philip [mailto:Philip.Watkins at eu.sony.com]
> Sent: Friday, June 20, 2003 11:19 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Workflows stopping due to deadlock on INDX
>
>
>  We have the situation where some work flows are in process but will not
> continue. A background task has finished and marked as complete but the next
> step in the workflow is not reached. At the time of the problem we can
> see(ST22) that there were SQL -913 errors on table INDX on the
> Get_task_index call in SAPLRHW0. Unsure of
> cause of the deadlocks but we could not restart the workflows that had
> frozen as no steps in 'ERROR'.How should we deal with this situation?
>  I tried to change the status of the last completed step to Error so that I
> could then restart but once an item is complete the function modules do not
> allow update to error. We believe the next step was not created because the
> workflow id could not be returned from INDX.
>
> Has anyone had this problem before and been able to re-start the workflows
>
>   Regards
>     Phil
>
>
>
> ****************************************************************************
> ****
> ***************
> The information contained in this message or any of its attachments may be
> confidential and is intended for the exclusive use of the addressee(s). Any
> disclosure, reproduction, distribution or other dissemination or use of this
> communication is strictly prohibited without the express permission of the
> sender. The views expressed in this email are those of the individual and
> not
> necessarily those of Sony or Sony affiliated companies. Sony email is for
> business use only.
>
> This email and any response may be monitored by Sony United Kingdom Limited.
> (6)
> ****************************************************************************
> ****
> ***************
>
>
> ***********************************************************************************************
> The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only.
>
> This email and any response may be monitored by Sony United Kingdom Limited.
> (04)
> ***********************************************************************************************