[Fwd: Fwd: Re: Error WL 864: Background job SWWDHEX cannot be scheduled (err or 6)]
Kouw, FA - SPLTX
fa.kouw at td.klm.com
Mon Jul 14 05:19:43 EDT 2003
Hello Kjetil,
We do NOT have hundreds of deadlines each day (as I explained in my mail). So I think it's best to use non-scheduled deadline monitoring. Do you
agree?
Regards,
Fred
Kjetil Kilhavn wrote:
> You say you have hundreds of deadlines each day. If I were you I would set
> up automatic rescheduling somewhere between three minutes (maximum of 480
> jobs per day) and ten minutes (maximum of 144 jobs per day). Since the job
> will reschedule itself after it has finished you will never have two
> instances running unless you set it up twice yourself.
>
> Kjetil Kilhavn
>
> "Kouw, FA - SPLTX"
> <fa.kouw at td.klm.com> To: SAP-WUG at MITVMA.MIT.EDU
> Sent by: SAP cc: (bcc: Kjetil Kilhavn)
> Workflow Subject: [Fwd: Fwd: Re: Error WL 864: Background job SWWDHEX cannot be scheduled (err or 6)]
> <Owner-SAP-WUG at MITVM
> A.MIT.EDU>
>
> 11.07.2003 16:37
> Please respond to
> "SAP Workflow Users'
> Group"
>
> Mike, Jocelyn,
>
> First of all, thanks for your input. I've not been able to respond due
> to workload... I changed my e-mail adress so I'll have the opportunity
> to view the postings more frequently.
>
> We are also on 4.6C, one client on the production system and the job is
> scheduled 'as needed' (when a workitem with a deadline is created). We
> do not have many workflows/workitems in which the deadlines are set, so
> I think I should keep this as is.
>
> The problem didn't occur since I reported it on this maillist. If it
> does I'll use your advise to (try to) solve it.
>
> Regards and thanks again,
>
> Fred Kouw
>
> **********************************************************************
> This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the addressee, you
> are notified that no part of the e-mail or any attachment may be disclosed,
> copied or distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received
> this e-mail by error, please notify the sender immediately by return
> e-mail,
> and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> subsidiaries and/or its employees shall not be liable for the incorrect or
> incomplete transmission of this e-mail or any attachments, nor responsible
> for any delay in receipt.
> **********************************************************************
>
> _____________________________________________________________________________________________
>
> This outbound message from KPN has been checked for all known viruses by
> KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
>
> ----- Message from "Fred Lunaspa" <fredlunaspa at hotmail.com> on Fri, 11 Jul
> 2003 16:29:27 +0200 -----
>
> To: fa.kouw at td.klm.com
>
> Subject: Fwd: Re: Error WL 864: Background job SWWDHEX cannot be
> scheduled (err or 6)
>
> >From: "Dart, Jocelyn" <jocelyn.dart at sap.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 (err
> >or 6)
> >Date: Thu, 3 Jul 2003 09:14:16 +0200
> >
> >Yes ok Mike,
> >The problem under individual-case monitoring the job is scheduled every
> >time a work item with a deadline set on it is created - not just when
> >deadlines are exceeded. So while your job will be rescheduled,
> essentially
> >you are just filling up your batch queue with redundant jobs. Your users
> >may not notice until the batch queue gets clogged but your system
> >administrators might not be so blasi.
> >
> >So the when you calculate the deadlines per minute - do it on the basis of
> >the number of work items being created with deadline times set on them,
> not
> >on the number of work items with deadlines exceeded.
> >
> >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: Wednesday,2 July 2003 5:52 PM
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: Error WL 864: Background job SWWDHEX cannot be scheduled (err
> >or 6)
> >
> >
> >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/
>
> _________________________________________________________________
> MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
>
> _________________________________________________________________________________________
>
> This inbound message from KPN has been checked for all known viruses by KPN
> IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and delete
> this message.
> Thank you.
>
> _________________________________________________________________________________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************
_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________
More information about the SAP-WUG
mailing list