Error WL 864: Background job SWWDHEX cannot be scheduled (err or 6)
Michael Pokraka
workflow at quirky.me.uk
Wed Jul 2 03:51:40 EDT 2003
Hi Jocelyn,
Agreed, I also discovered something else: I used to use SM37 to see how often it runs - this is where I got my 20 times/day from.
However I've since discovered at this site (4.6c) that there are hundreds of deadlines each day, and the job just keeps falling over but usually gets rescheduled when a new deadline is created... thus nobody notices the problem, and I see no reason to schedule it regularly :)
I'll change it to run scheduled and see if the problem goes away.
Incidentally, the SAP docs recommend to "Only select permanent deadline monitoring if there are several deadlines to be monitored per minute."
Thanks for your input,
Cheers
Mike
On Tue, Jul 01, 2003 at 02:18:46AM +0200, Dart, Jocelyn wrote:
> Hi Mike,
> I don't think I'd make that assumption about "safeguarding against self-duplication" I doubt if the mechanism is that sophisticated as it was developed a while ago. The running on an "as-needed" basis sounds to me like a problem - in production it should really be running in periodic mode not in individual case mode. Try chaning your config for deadline monitoring.
> Regards,
> Jocelyn Dart
> Consultant (SRM, EBP, Workflow)
> and co-author of the book
> "Practical Workflow for SAP"
> SAP Australia
> email: jocelyn.dart at sap.com
> phone: +61 412 390 267
> fax: +61 2 9935 4880
>
>
>
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Sent: Monday,30 June 2003 10:41 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Error WL 864: Background job SWWDHEX cannot be scheduled (err or 6)
>
>
> Hi Jocelyn,
> The job runs on an as needed basis, currently it schedules itself around 20 times/day. I would imagine it should have safeguards against 'self-duplication' - even if it only runs twice a day, it can still happen concurrently.
>
> Hold that thought, I've finally found relating entries in the system log:
> EGZ BP_JOB_MODIFY: Job cannot be modified. Reason:
> EGE > Job SWWDHEX is not in table TBTCO
> EGC > Job SWWDHEX is currently locked
> EGC > Job SWWDHEX is currently locked
> EGC > Job SWWDHEX is currently locked
>
> Fred - I've also found an OSS note 69470 which deals with a concurrency issue between SWWDHEX and SAP_REORG_JOBS. In our case however the error happened at 8:30 and SAP_REORG_JOBS ran at 0:30. Back to the drawing board.
>
> Cheers
> Mike
>
> On Mon, Jun 30, 2003 at 06:54:37AM +0200, Dart, Jocelyn wrote:
> > Mike, Have you checked the timings? Might be a time overlap issue if a previously scheduled job is still active when you try to schedule the job again. You might need to adjust the job frequency.
> > Regards,
> > Jocelyn Dart
> > Consultant (SRM, EBP, Workflow)
> > and co-author of the book
> > "Practical Workflow for SAP"
> > SAP Australia
> > email: jocelyn.dart at sap.com
> > phone: +61 412 390 267
> > fax: +61 2 9935 4880
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> > Sent: Friday,27 June 2003 8:21 PM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: Re: Error WL 864: Background job SWWDHEX cannot be scheduled (err or 6)
> >
> >
> > FWIW, I'm also trying to track down the same error, single production client, happens once or twice a week - seemingly at random.
> > I'll post if I find any answer.
> > Cheers
> > Mike
> >
> > On Fri, Jun 27, 2003 at 01:32:20AM +0200, Dart, Jocelyn wrote:
> > > Hi Fred,
> > > You wouldn't happen to be running workflow in multiple clients of that same system would you?
> > > I've had this message when you try to schedule the job in one client when its already been scheduled
> > > in another client.
> > > In which case the answer is to create your own job for each client, e.g. SWWERRExxx where xxx is the client number.
> > > Regards,
> > > Jocelyn Dart
> > > Consultant (SRM, EBP, Workflow)
> > > and co-author of the book
> > > "Practical Workflow for SAP"
> > > SAP Australia
> > > email: jocelyn.dart at sap.com
> > > phone: +61 412 390 267
> > > fax: +61 2 9935 4880
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Fred Lunaspa [mailto:fredlunaspa at hotmail.com]
> > > Sent: Friday,27 June 2003 12:57 AM
> > > To: SAP-WUG at MITVMA.MIT.EDU
> > > Subject: Re: Error WL 864: Background job SWWDHEX cannot be scheduled (error 6)
> > >
> > >
> > > Thanks Namit !
> > >
> > > I rescheduled the background job (program RSWWDHEX) and restarted the
> > > workflow (SWPR). All works well now. I've no idea why the job couldn't be
> > > scheduled, no client copy of refresh was done at that time. Hopefully it
> > > doesn't occur many times...
> > >
> > > Regards,
> > >
> > > Fred
> > >
> > > >From: Namit Bhargava <namit.bhargava at us.ibm.com>
> > > >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> > > >To: SAP-WUG at MITVMA.MIT.EDU
> > > >Subject: Re: Error WL 864: Background job SWWDHEX cannot be scheduled
> > > >(error 6)
> > > >Date: Thu, 26 Jun 2003 08:49:31 -0400
> > > >
> > > >Try rescheduling the background job (ask someone who has the required
> > > >autho. BASIS Team) and then reprocess the workitem. This usually happens
> > > >when a client copy is made or the system refreshed/rebooted.
> > > >
> > > >Thanks & regards,
> > > >____________________________________________
> > > >Namit Bhargava
> > > >Sr. IT Specialist (EAI, SAP Workflow & ABAP)
> > > >IBM Global Services - AMS/eBI
> > > >
> > > >Internet: namit.bhargava at us.ibm.com
> > > >Telephone: Office (215) 832-1737 Cell (215) 668-6929
> > > >
> > > >
> > > >
> > > > Fred Lunaspa
> > > > <fredlunaspa at hotmai To:
> > > >SAP-WUG at MITVMA.MIT.EDU
> > > > l.com> cc:
> > > > Sent by: SAP Subject: Error WL 864:
> > > >Background job SWWDHEX cannot be scheduled (error 6)
> > > > Workflow
> > > > <Owner-SAP-WUG at MITV
> > > > MA.MIT.EDU>
> > > >
> > > >
> > > > 06/26/2003 08:43 AM
> > > > Please respond to
> > > > "SAP Workflow
> > > > Users' Group"
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >Hello,
> > > >
> > > >One of our workflows ran into error. The error is:
> > > >
> > > >- Error WL 864: Background job SWWDHEX cannot be scheduled (error 6)
> > > >
> > > >This means the deadline monitoring background job cannot be scheduled, but
> > > >I
> > > >wasn't able to figure out why. The workflow has been deactivated yesterday
> > > >(this instance was created before yesterday, the instance ran into error
> > > >this morning, thus 1 day after the workflow has been deactivated). Could
> > > >the
> > > >deactivation of the workflow be the reason the error occurred or must I
> > > >find
> > > >a solution elsewhere?
> > > >
> > > >Regards,
> > > >
> > > >Fred Kouw
> > > >
> > > >_________________________________________________________________
> > > >MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
> > >
> > > _________________________________________________________________
> > > Hotmail en Messenger on the move
> > > http://www.msn.nl/communicatie/smsdiensten/hotmailsmsv2/
More information about the SAP-WUG
mailing list