Memory problems

Mike Gambier madgambler at hotmail.com
Thu Oct 12 05:48:38 EDT 2006


I would hazard a guess that you are blowing your rollback segment in 
whatever database you are using.

The dump may well tell you about the backend databse issue if you look hard 
enough, e.g. ORA error code if you're using Oracle.

Try executing a COMMIT WORK at the end of a block of, say, 100 calls to the 
FM.

MGT

>From: "Maes Steven" <Steven.Maes at luminus.be>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: <sap-wug at mit.edu>
>Subject: Memory problems
>Date: Thu, 12 Oct 2006 11:08:45 +0200
>
>
>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





More information about the SAP-WUG mailing list