How to restart lots of workflows in 'STARTED' status - PROBLEM SOLVED !
Dart, Jocelyn
jocelyn.dart at sap.com
Sun Feb 6 23:57:45 EST 2005
Good to hear you sorted it Ross. Thanks for letting everyone know how
you did it.
Add "better workflow administration tools" and "more WAPIs" to your
benefits-of-upgrading list.
Regards,
Jocelyn
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Michael Pokraka
Sent: Friday,4 February 2005 8:18 PM
To: SAP Workflow Users' Group
Subject: Re: How to restart lots of workflows in 'STARTED' status -
PROBLEM SOLVED !
Hi Ross,
Good to hear that you got your problem resolved, but expect a grilling
from
Jocelyn about your use of SQL :-)
The 4.6 equivalent to SAP_WAPI_SET_ERROR is SWW_WI_STATUS_CHANGE_NEW.
Not for
us plebs to use either, but much preferred over SQL. Then for parts 2
and 3
(I'd forgotten about this one in my earlier reply), there's SWPR to do
the
whole shebang in one go.
Cheers
Mike
--- Ross.Cresdee at iag.com.au wrote:
>
>
************************************************************************
**
>
> Note: This e-mail is subject to the disclaimer contained at the bottom
> of this message.
>
>
************************************************************************
**
> :
>
> Hi All,
>
> Thanks to all those who suggested remedies to our problem of hanging
> workflows in 'STARTED' status. I neglected to mention that we are
running
> SAP 46B which meant some of the newer workflow utilities weren't
available.
>
> We actually used a hybrid of the suggested solutions to resolve our
problem
> :
>
> 1. Using SQL we reset all the workflows' child task status in
SWWWIHEAD
> created over a certain date range that were hanging in WAITING status
to
> 'ERROR' status.
>
> 2. Selected all workflow id's (WI_ID) in ERROR for that day into an
> internal table
>
> 3. Looped through this table applying function
SWW_WI_ADMIN_ERROR_RESTART
> to all the WI_ID.
>
> The result was very pleasing with over 1000 workflows restarted
cleanly and
> in quick time. It was all done in a bit of a rush so we're going to
review
> the suggestions again to ensure we're better prepared for next time
(if
> ever) !
>
> Thanks again. Much appreciated.
>
> Ross.
>
>
>
>
>
> Ross
>
> Cresdee/NSW/NRMA@ To:
sap-wug at mit.edu
>
> NRMA cc:
>
> Sent by: Subject: How to
restart lots
> of workflows in 'STARTED' status
> sap-wug-bounces at m
>
> it.edu
>
>
>
>
>
> 03/02/2005 05:03
>
> PM
>
> Please respond to
>
> "SAP Workflow
>
> Users' Group"
>
>
>
>
>
>
>
>
>
>
************************************************************************
**
>
> Note: This e-mail is subject to the disclaimer contained at the bottom
> of this message.
>
>
************************************************************************
**
> :
> Hi People,
>
> I hope you can give me a few clues. We've got a situation where
hundreds
> of workflows have been in 'STARTED' status for over a week. The
workflows
> had reached a task that paused for 10 seconds and there they waited.
Our
> deadline monitoring job was not running while these hanging workflows
> accumulated but the workflows did not take off once the job was
restarted.
> We've noted that we can force each workflow to manually complete but
we
> don't want to have to do this for hundreds of workflows one at a time.
>
> Is there a way of restarting all these workflow that are in status
> 'STARTED' but are waiting for a time in the past ?
>
> Thanks for any assistance.
>
> Regards, Ross.
>
>
>
> :
>
************************************************************************
********
>
> The information transmitted in this message and attachments (if any)
> is intended only for the person or entity to which it is addressed.
> The message may contain confidential and/or privileged material.
> Any review, retransmission, dissemination or other use of, or taking
> of any action in reliance upon this information, by persons or
entities
> other than the intended recipient is prohibited.
>
> If you have received this in error, please contact the sender and
delete
> this
> e-mail and associated material from any computer.
>
> The intended recipient of this e-mail may only use, reproduce,
disclose or
> distribute the information contained in this e-mail and any attached
files,
> with the permission of the sender.
>
> This message has been scanned for viruses and cleared by MailMarshal.
>
> ********************************************************************
> :
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
>
>
> :
>
************************************************************************
********
>
> The information transmitted in this message and attachments (if any)
> is intended only for the person or entity to which it is addressed.
> The message may contain confidential and/or privileged material.
> Any review, retransmission, dissemination or other use of, or taking
> of any action in reliance upon this information, by persons or
entities
> other than the intended recipient is prohibited.
>
> If you have received this in error, please contact the sender and
delete this
> e-mail and associated material from any computer.
>
> The intended recipient of this e-mail may only use, reproduce,
disclose or
> distribute the information contained in this e-mail and any attached
files,
> with the permission of the sender.
>
> This message has been scanned for viruses and cleared by MailMarshal.
>
> ********************************************************************
> :
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
More information about the SAP-WUG
mailing list