SWN_SELSEN dump problem
Rick Bakker
rbakker at gmail.com
Mon Aug 23 15:36:09 EDT 2010
Hello,
Unfortunately, having a SWN_TIMESTAMPS entry isn't enough, the timestamp
itself has to be not too far in the past for it to run in a reasonable time.
regards
Rick Bakker
Hanabi Technology
On Mon, Aug 23, 2010 at 7:36 AM, Morris, Eddie <eddie.morris at sap.com> wrote:
> Hi,
>
>
>
> Try running RSWWWIDE_DEP on tables SWWUSERWI and SWWORGTASK and remove any
> obsolete entries. Then try running SWN_SELSEN again.
>
>
>
> Regards,
>
> Eddie
>
>
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *srinivas
> *Sent:* 23 August 2010 12:57
>
> *To:* SAP Workflow Users' Group
> *Subject:* Re: SWN_SELSEN dump problem
>
>
>
> Hi Rick,
>
>
>
> I checked the dump file,the time out error is getting at different select
> statement and I checked the table SWN_TIMESTAMPS and found the
> zdelivery entry what I have customized in SWNCONFIG. Does this mean the time
> stamp created ?? If I run the report SWN_SELSEN again will it work?? Because
> I dont have access to run the report in Production system I need to raise a
> request for this.
>
> 52
>
>
> IF NOT read_org_task IS INITIAL.
>
> >>>>>
>
>
> SELECT * FROM swworgtask INTO TABLE loc_org_task
>
> 54
>
>
> WHERE wi_id = wi_id
>
> 55
>
>
> AND no_sel = space.
>
> 56
>
>
> ELSE.
>
> 57
>
>
> * use given entries
>
> 58
>
>
> loc_org_task[] = act_org_task[].
>
> 59
>
>
>
>
> 60
>
>
> DELETE loc_org_task WHERE wi_id <> wi_id
>
> 61
>
>
> OR no_sel <> space.
>
> 62
>
> ENDIF.
>
>
>
> On Sat, Aug 21, 2010 at 8:42 PM, Rick Bakker <rbakker at gmail.com> wrote:
>
> Hello,
>
> If you can't go the route of changing the SWN_TIMESTAMPS table (which
> Florin managed to do, see my prvious mail) then maybe you could set up
> some filters first to split up the tasks (TS......) so that not all of
> them are done at once.
>
>
> regards
> Rick Bakker
> Hanabi Technology
>
> On Sat, Aug 21, 2010 at 2:08 AM, srinivas <ootasrinivasreddy at gmail.com>
> wrote:
> > Hi Rick and Sarawana,
> >
> > I have scheduled a batch job for SWN_SELSEN report in production, after
> > running for 23.5 hrs the report agian gone to dump.Any suggetions??
> >
> > On Thu, Aug 19, 2010 at 11:26 PM, srinivas <ootasrinivasreddy at gmail.com>
> > wrote:
> >>
> >> Hi Rick,Sarawana and all,
> >>
> >> Thanks for your inputs. I have executed SWN_SELSEN in background for
> the
> >> first time,as per your inputs may be this program will take a lot of
> time
> >> for the first time but going forward after the first run I assume and
> wish
> >> this program should consume less time.
> >>
> >> On Thu, Aug 19, 2010 at 12:04 AM, Rick Bakker <rbakker at gmail.com>
> wrote:
> >>>
> >>> Hello,
> >>>
> >>> Earlier this year, Florin Wach (who I believe had the same problem)
> >>> wrote in this mailing list:
> >>>
> >>> <quote>
> >>> I'm already using only DELTA filters, although there is an ALL_FULL
> >>> filter, but this is not checked at the selection, so it's there, but
> >>> it's not active.
> >>>
> >>> I have debugged down to the SELECT statement and tracked back to where
> >>> the timestamp was read. In fact, although the DELTA filter was used,
> >>> the ALL_FULL still throws in between (probably, when the DELTA filter
> >>> has no timestamp set itself).
> >>>
> >>> With the hint from Rick I could manually create a time stamp entry for
> >>> DELTA, using the ABAP OO class CL_SWN_FILTER, create an instance,
> >>> execute method LOAD_INSTANCE, use ID=WORKLOW, SCENARIO=STANDARD (or
> >>> whatever was appropriate), then select the interface IF_SWN_FILTER and
> >>> execute method SET_LAST_APPLIED and... e voila ... enter the TimeStamp
> >>> number here. (I have written a small report to run in the D-System to
> >>> write the timestamp to copy it into that field. It's basically the
> >>> exact format, Rick gave).
> >>> <unquote>
> >>>
> >>> I hope it helps.
> >>>
> >>> regards
> >>> Rick Bakker
> >>> Hanabi Technology
> >>>
> >>>
> >>> On Wed, Aug 18, 2010 at 12:40 PM, Vijayakumar, Sarawana K
> >>> <Sarawana.Vijayakumar at energyeast.com> wrote:
> >>> > Following is some information I learned when I faced this problem.
> Hope
> >>> > it helps other users.
> >>> >
> >>> > As everyone might know, a timeout occurs at the select statement
> >>> > indicated in the dump Srinivas had given in earlier posts.
> >>> >
> >>> > Whenever SWN_SELSEN is run, it looks at entries in table
> SWN_TIMESTAMPS
> >>> > to see when the program was run last for a given delivery
> >>> > schedule/filter/selection schedule. If the program is being called
> for the
> >>> > first time then there is no entry in this table and the timestamp is
> set to
> >>> > all zeros. In such a case, a sequential read of the SWWLOGHIST table
> will be
> >>> > done to get work items created after the timestamp in hand (which is
> all
> >>> > zeros). So depending upon the number of entries in table SWWLOGHIST
> it will
> >>> > take a long time. And thanks to the inner join on the SWWWIHEAD in
> the same
> >>> > select statement, it takes even longer than that!
> >>> >
> >>> > But once this program runs successfully, the time is recorded in the
> >>> > SWN_TIMESTAMPS table for the given delivery
> schedule/selection/filter. And
> >>> > when it runs the next time it selects WIs from SWWLOGHIST which were
> created
> >>> > only after this timestamp.
> >>> >
> >>> > In sandbox system I was able to run this program in debug mode and
> >>> > change the timestamp at the select statement to a very recent time
> (like
> >>> > right now!) and allowed the rest of the program to run. It completed
> in a
> >>> > jiffy. The next time I ran the program, no problems, it completes
> within
> >>> > seconds. My development has not been in QA or PRD, and I know going
> in debug
> >>> > mode is not an option.
> >>> >
> >>> > But if any user can give me a way to update the timestamp, it will
> put
> >>> > an end to this problem.
> >>> >
> >>> > Thank you,
> >>> > -Sarawana
> >>> >
> >>> >
> >>> >
> >>> > -----Original Message-----
> >>> > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> >>> > Behalf Of sap-wug-request at mit.edu
> >>> > Sent: Wednesday, August 18, 2010 12:06 PM
> >>> > To: sap-wug at mit.edu
> >>> > Subject: SAP-WUG Digest, Vol 69, Issue 36
> >>> >
> >>> > Send SAP-WUG mailing list submissions to
> >>> > sap-wug at mit.edu
> >>> >
> >>> > To subscribe or unsubscribe via the World Wide Web, visit
> >>> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >>> > or, via email, send a message with subject or body 'help' to
> >>> > sap-wug-request at mit.edu
> >>> >
> >>> > You can reach the person managing the list at
> >>> > sap-wug-owner at mit.edu
> >>> >
> >>> > When replying, please edit your Subject line so it is more specific
> >>> > than "Re: Contents of SAP-WUG digest..."
> >>> >
> >>> >
> >>> > Today's Topics:
> >>> >
> >>> > 1. SWN_SELSEN dump (Karl Nietz)
> >>> >
> >>> >
> >>> >
> ----------------------------------------------------------------------
> >>> >
> >>> > Message: 1
> >>> > Date: Wed, 18 Aug 2010 11:44:31 +1100
> >>> > From: Karl Nietz <knietz at csc.com.au>
> >>> > Subject: SWN_SELSEN dump
> >>> > To: sap-wug at mit.edu
> >>> > Message-ID:
> >>> >
> >>> > <OF8503395E.9040788E-ONCA257783.0003E141-CA257783.0004142E at csc.com>
> >>> > Content-Type: text/plain; charset="us-ascii"
> >>> >
> >>> > Hi,
> >>> > Check the size of the workflow log history file. If it is massive
> then
> >>> > this can cause this error. You may wish to experiment by running the
> >>> > program with the Delta filter only. Or run archiving to reduce the
> >>> > size
> >>> > of the file.
> >>> >
> >>> > Karl Nietz
> >>> >
> >>> > Check this note
> >>> > Note 1105696 - WF Notif: Memory consumption and performance of
> >>> > SWN_SELSEN
> >>> >
> >>> > Regards,
> >>> > Imthiaz
> >>> >
> >>> > -----Original Message-----
> >>> > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> >>> > Behalf
> >>> > Of
> >>> > sap-wug-request at mit.edu
> >>> > Sent: Tuesday, August 17, 2010 2:45 PM
> >>> > To: sap-wug at mit.edu
> >>> > Subject: SAP-WUG Digest, Vol 69, Issue 33
> >>> >
> >>> > Send SAP-WUG mailing list submissions to
> >>> > sap-wug at mit.edu
> >>> >
> >>> > To subscribe or unsubscribe via the World Wide Web, visit
> >>> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >>> > or, via email, send a message with subject or body 'help' to
> >>> > sap-wug-request at mit.edu
> >>> >
> >>> > You can reach the person managing the list at
> >>> > sap-wug-owner at mit.edu
> >>> >
> >>> > When replying, please edit your Subject line so it is more specific
> >>> > than "Re: Contents of SAP-WUG digest..."
> >>> >
> >>> >
> >>> > Today's Topics:
> >>> >
> >>> > 1. SWN_SELSEN going to dump (srinivas)
> >>> > 2. SWN_SELSEN dump result (srinivas)
> >>> > 3. Re: SWN_SELSEN dump result (Rick Bakker)
> >>> > 4. Re: SWN_SELSEN dump result (srinivas)
> >>> >
> >>> >
> >>> >
> ----------------------------------------------------------------------
> >>> >
> >>> > Message: 1
> >>> > Date: Tue, 17 Aug 2010 22:05:44 +0530
> >>> > From: srinivas <ootasrinivasreddy at gmail.com>
> >>> > Subject: SWN_SELSEN going to dump
> >>> > To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >>> > Message-ID:
> >>> > <AANLkTimgn-3SOuV2XFr5RCra7+gB9OR+_-=X3xC547y_ at mail.gmail.com>
> >>> > Content-Type: text/plain; charset="iso-8859-1"
> >>> >
> >>> > Hi All,
> >>> >
> >>> > While executing the report SWN_SELSEN (extended notifications) via
> >>> > batch
> >>> > job
> >>> > or manually the report is going to dump.Can someone tell me what are
> >>> > the
> >>> > possible causes for the dump in SWN_SELSEN??Actually I dont have dump
> >>> > file
> >>> > at the moment,this issue is happening in production server.
> >>> >
> >>> > --
> >>> > Thanks and Regards
> >>> > Srini..
> >>> > -------------- next part --------------
> >>> > An HTML attachment was scrubbed...
> >>> > URL:
> >>> >
> >>> >
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20100817/8bcbfbd8/attac
> >>> >
> >>> > hment-0001.htm
> >>> >
> >>> > ------------------------------
> >>> >
> >>> > Message: 2
> >>> > Date: Tue, 17 Aug 2010 23:04:06 +0530
> >>> > From: srinivas <ootasrinivasreddy at gmail.com>
> >>> > Subject: SWN_SELSEN dump result
> >>> > To: "SAP Workflow Users' Group" <sap-wug at MIT.EDU>
> >>> > Message-ID:
> >>> > <AANLkTikKNvHRDLvJxBwObAOGnAMn1b0a3p4S+9n283GX at mail.gmail.com<AANLkTikKNvHRDLvJxBwObAOGnAMn1b0a3p4S%2B9n283GX at mail.gmail.com>
> >
> >>> > Content-Type: text/plain; charset="iso-8859-1"
> >>> >
> >>> > Hi All,
> >>> >
> >>> > Below is the dump result when the report SWN_SELSEN is executed. Does
> >>> > this
> >>> > issue related to memory??
> >>> >
> >>> >
> >>> > Memory consumption
> >>> > Roll.... 16192
> >>> > EM...... 12569520
> >>> > Heap.... 0
> >>> > Page.... 90112
> >>> > MM Used. 2145408
> >>> > MM Free. 2041808
> >>> >
> >>> > --
> >>> > Thanks and Regards
> >>> > Srini..
> >>> > -------------- next part --------------
> >>> > An HTML attachment was scrubbed...
> >>> > URL:
> >>> >
> >>> >
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20100817/2578f7f7/attac
> >>> >
> >>> > hment-0001.htm
> >>> >
> >>> > ------------------------------
> >>> >
> >>> > Message: 3
> >>> > Date: Tue, 17 Aug 2010 13:01:40 -0500
> >>> > From: Rick Bakker <rbakker at gmail.com>
> >>> > Subject: Re: SWN_SELSEN dump result
> >>> > To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >>> > Message-ID:
> >>> > <AANLkTikZGSUyM8GwXfFc+kecQsDGHz9UX+=R53TYH_6F at mail.gmail.com>
> >>> > Content-Type: text/plain; charset=ISO-8859-1
> >>> >
> >>> > Hello,
> >>> >
> >>> > Doesn't the dump show any sort of error?
> >>> >
> >>> > Has it been working in the past?
> >>> > Check also SLG1.
> >>> >
> >>> > regards
> >>> > Rick Bakker
> >>> > Hanabi Technology
> >>> >
> >>> > On Tue, Aug 17, 2010 at 12:34 PM, srinivas
> >>> > <ootasrinivasreddy at gmail.com>
> >>> > wrote:
> >>> >>
> >>> >> Hi All,
> >>> >>
> >>> >> Below is the dump result when the report SWN_SELSEN is executed.
> Does
> >>> > this
> >>> >> issue related to memory??
> >>> >>
> >>> > -------------- next part --------------
> >>> > An HTML attachment was scrubbed...
> >>> > URL:
> >>> >
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20100818/0f46b8dc/attachment-0001.htm
> >>> >
> >>> > ------------------------------
> >>> >
> >>> > _______________________________________________
> >>> > SAP-WUG mailing list
> >>> > SAP-WUG at mit.edu
> >>> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >>> >
> >>> >
> >>> > End of SAP-WUG Digest, Vol 69, Issue 36
> >>> > ***************************************
> >>> >
> >>> > _______________________________________________
> >>> > 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
> >>
> >>
> >>
> >> --
> >> Thanks and Regards
> >> Srini..
> >> SAP Technical Consultant
> >> srinivasa.reddy.oota at sap.com
> >> +919886760677
> >>
> >
> >
> >
> > --
> > Thanks and Regards
> > Srini..
> >
> > _______________________________________________
> > 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
>
>
>
>
> --
> Thanks and Regards
> Srini..
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100823/62b56fa9/attachment.htm
More information about the SAP-WUG
mailing list