rswwdhex - job gets cancelled due to locking issue

[Susan R. Keohan]

Hi Dave,

I didn't see any SM12 entries, but then again, the job failed to reschedule at 7:30 last night, and 
*surprise!* I was not logged on!  It seems from the system log that the job is locking itself out, 
not a data locking issue.  But that's just my take on it.

Thanks!
Sue

Dave Weston wrote:

> Hi Sue, any entries in SM12 for this job ? When they rescheduled the job were all job entries deleted first and then rescheduled ? Probably hard to tell as basis did it.
>  
> Cheers
> Dave
> 
> ________________________________
> 
> From: sap-wug-bounces at mit.edu on behalf of Susan R. Keohan
> Sent: Tue 7/12/2005 8:34 AM
> To: sap-wug at mit.edu
> Subject: rswwdhex - job gets cancelled due to locking issue
> 
> 
> 
> Hi all,
> 
> We are running on R/3 4.6c.
> 
> We had RSWWDHEX running without incident until last September, when it stopped, I don't know why.
> When the matter was brought to my attention, we re-scheduled it via SWWB (or is it SWWA, I can't be
> sure because Basis does it).  The interval between runs is 20 minutes, which should be sufficient,
> since there are probably less than 5 workitems 'waiting' for a deadline at any given time.
> 
> Anyway, the job gets finishes, but fails to reschedule itself daily (no specific time, it could fail
> to reschedule at 5:30, it could fail to reschedule at 7:30...).  The system log from SM21 says
> 'Job SWWDHEX is currently locked'  and the detail entry follows:
> 
> 
>>Within background processing, it was found that the specified job is      
>>being edited, for example, another user edits the job or the run-time     
>>system of background processing is accessing the job. Please attempt to   
>>execute the action required by you with the job at a later date.          
>>                                                                          
>>If, in spite of repeated attempts, this should not be successful, that    
>>could be related to problems in the locking system (enqueue server): For  
>>example, "locking corpses" could be available. Please check that with     
>>the transaction SM12. You can also test the function efficiency of your   
>>locking system there by means of the displayed diagnosis.                 
>>                                                                          
> 
> 
> I am sure we can reschedule with a longer interval between runs, but not sure if this will actually
> solve the problem.  Has anyone out there dealt with this ?  OSS, and SDN search of this archive
> yield no joy.
> 
> Happy WF-ing!
> Sue
> --
> Susan R. Keohan
> SAP Workflow Developer
> MIT Lincoln Laboratory
> 244 Wood Street
> LI-200
> Lexington, MA. 02420
> 781-981-3561
> keohan at ll.mit.edu
> _______________________________________________
> 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

-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu