Memory problems

[Maes Steven]

Phil, Mike, Mike,

Thx for your answers ...

Steven

-----Oorspronkelijk bericht-----
Van: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Namens
Soady, Phil
Verzonden: donderdag 12 oktober 2006 11:54
Aan: SAP Workflow Users' Group
Onderwerp: RE: Memory problems

if you google or see Service.sap.com for  TSV_TNEW_PAGE_ALLOC_FAILED
you will find the rz10 parameter to make more roll available.

In addition, you can look at reduce the overall size the  packet of
work.
Commit work may.

See also FREE TABLE statement to release memory consumed no longer
required.

otherwise... try SDN for ABAP support.

Cheers



Phil Soady
Solution Architect
Netweaver Consulting
SAP Australia
M  +61 412 213 079
F  +61 2 9957 7263
mailto:phil.soady at sap.com


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Maes Steven
Sent: Thursday, 12 October 2006 7:09 PM
To: sap-wug at mit.edu
Subject: Memory problems


Hi,

Interesting problem :

We trigger several workflows (+/- 3000) by a program using function
module SWW_WI_START_SIMPLE.

After +/- 2000 workflows, the system dumps with a SYSTEM_NO_ROLL or
TSV_TNEW_PAGE_ALLOC_FAILED. In both cases there is a memory problem for
the extension of an internal table.

My question :

Is it enough to do a "Commit work" after function SWW_WI_START_SIMPLE or
is there a function module/system command/abap command to clear the
buffer/internal table ?

Cheers,

Steven

-------------------Disclaimer-------------------
http://www.luminus.be/disclaimer
------------------------------------------------

_______________________________________________
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

-------------------Disclaimer-------------------
http://www.luminus.be/disclaimer
------------------------------------------------