Skip to Content
author's profile photo Former Member
Former Member

SWWDHEX is runnig for long

Hi experts,

in production system there is a job SWWDHEX which is running for long time around 16000 seconds and using all the system

work processes and hanging all other batch jobs.

could you please guide me how to resolve this problem.

how should is proceed ??

why we use this job?

what will happen if i will cancel this job in between?

can we stop ececuting this job?

please guide me i am new ot this.

thanks in advance

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 07, 2010 at 03:18 PM

    I faced a similar issue.

    1. Check SM50 transacton. Are all Dialog work processes occupied? If yes, which program / table are they struck at?

    2. In my case, the program was struck at updading the table SWFREVTLOG, which is the table for Event logs.

    3. If the same is happening in your case, then you should switch off the event log (transaction SWELS) and kill all the instances of the SWWDHEX (if there are multiple instanced running) job. Then start a single instance of the job and let it process all the deadlines.

    4. You should also see a huge queue in SM58, do not let another instance of SWWDHEX start till the existing queue is cleared.

    Does this help?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 07, 2010 at 10:07 PM

    how should is proceed ??

    As Raghavendra suggested, if the long runs are due to event trace please switch off event trace in transaction SWELS and you can delete trace entries from transaction SWEL to reduce number of entries in table.

    why we use this job?

    This job is to evaluate workflow dead lines

    what will happen if i will cancel this job in between?

    You can cancel the current job and start new job after fixing the rootcause (after deleting event trace entries)

    can we stop ececuting this job?

    If you are not using workflow dead line monitoring, yes you can stop executing report

    Hope this helps!!!

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.