rswwdhex - job gets cancelled due to locking issue

[Morris, Eddie]

Hi Susan,

Try doing a consistency check of the BTC Processing System as follows:
1. Run Transaction SM65
2. Select Goto ... Additional tests
3. select these options: Perform TemSe check
                         Consistency check DB tables
                         List
                         Check profile parameters
                         Check host names
                         Determine no. of jobs in queue
                         All job servers
   and then click execute.
4. Once you get the results check to see if you have any inconsistencies
   in any of your tables.
5. If there are any inconsistencies reported then run the "Background
   Procesing Analyses" (SM65 .. Goto ... Additional Tests) again.
   This time check the "Consistency check DB tables" and the
   "Remove Inconsistencies" options.
6. Run this a couple of times until all inconsistencies are removed from
   the tables.
Make sure you run this SM65 check when the system is quiet and no other
batch jobs are running as this would put a lock on the TBTCO table till
it finishes.  This table may be needed by any other batch job that is
running or scheduled to run at the time SM65 checks are running.

Regards,
Eddie

 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Susan R. Keohan
Sent: 12 July 12, 2005 13:34
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