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