<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: dump during processing on multiple work process. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026684#M1169367</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's the page allocation problem, try to minimize the background job in report1 or release the jobs batch by batch........ let us say at a time release 10 jobs and once the jobs are completed than release another set of jobs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sasi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Dec 2008 14:23:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-12-30T14:23:00Z</dc:date>
    <item>
      <title>dump during processing on multiple work process.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026681#M1169364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have designed a prohgram "report1" which creates variants for another program "report2" and schedules those variants in back ground on multiple work processess.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When run the "report1", it creates 19 variants for "report2" and those variants will be scheduled for background process on multiple workprocess.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is, when i execute "report1", out of 19 jobs 7 jobs have been cancelled due to dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------------------------------------" /&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;The dump analysis is as follows*&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Runtime errors         TSV_TNEW_PAGE_ALLOC_FAILED&lt;/P&gt;&lt;P&gt;Short dump has not been completely stored. It is too big.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;h1 No storage space available for extending the internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;What happened?*&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You attempted to extend an internal table, but the required space was&lt;/P&gt;&lt;P&gt;not available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;Error analysis*&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The internal table (with the internal identifier "IT_77") could not be&lt;/P&gt;&lt;P&gt;enlarged any further. To enable error handling, the internal table had&lt;/P&gt;&lt;P&gt;to be deleted before this error log was formatted. Consequently, if you&lt;/P&gt;&lt;P&gt;navigate back from this error log to the ABAP Debugger, the table will&lt;/P&gt;&lt;P&gt;be displayed there with 0 lines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the program was terminated, the internal table concerned returned&lt;/P&gt;&lt;P&gt;the following information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Line width: 1240&lt;/P&gt;&lt;P&gt;Number of lines: 340000&lt;/P&gt;&lt;P&gt;Allocated lines: 340000&lt;/P&gt;&lt;P&gt;New no. of requested lines: 10000 (in 1250 blocks).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;      Last error logged in SAP kernel*&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Component............ "EM"&lt;/P&gt;&lt;P&gt;Place................ "SAP-Server SR-3110_ISI_30 on host SR-3110 (wp 26)"&lt;/P&gt;&lt;P&gt;Version.............. 37&lt;/P&gt;&lt;P&gt;Error code........... 7&lt;/P&gt;&lt;P&gt;Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "&lt;/P&gt;&lt;P&gt;Description.......... " "&lt;/P&gt;&lt;P&gt;System call.......... " "&lt;/P&gt;&lt;P&gt;Module............... "emxx.c"&lt;/P&gt;&lt;P&gt;Line................. 1886.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt; Source code extract*&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;001640   FORM get_new_info .
001650
001660     DATA: wa_res LIKE zrisu_openitems_view,
001670           it_temp_final TYPE TABLE OF zrisu_openitems_view.
001680
001690     REFRESH: it_temp_final, it_final.
001700   * collect the free memory
001710     CALL METHOD cl_abap_memory_utilities=&amp;gt;do_garbage_collection.
001720
001730   * First find all the open FI document items on the system satisfying
001740   *  the selection criteria.
001750     SELECT opbel opupw opupk opupz gpart vtref vkont abwbl abwtp stakz
001760            waers studt betrw mahnv blart xblnr
001770            INTO CORRESPONDING FIELDS OF TABLE it_temp_final
001780            FROM dfkkop
001790            PACKAGE SIZE c_blksiz
001800            FOR ALL ENTRIES IN s_opbel
001810            WHERE opbel = s_opbel-low
001820              AND augst = space
001830              AND gpart IN s_part
001840              AND abwtp = space
001850              AND abwbl = space
001860              AND bldat IN s_bldat
001870              AND blart IN s_blart.
            APPEND LINES OF it_temp_final TO it_final.  ---&amp;gt; dump occurs at this statement
001890       REFRESH it_temp_final.
001900     ENDSELECT.
001910     REFRESH s_opbel.
001920
01930     SORT it_final BY opbel opupw opupk opupz.
01940
01950     LOOP AT it_final INTO wa_final.
01960   * Check the documentdate if relevant
01970       IF wa_res-opbel EQ wa_final-opbel.
01980   * Use information from last record  if same document  to make the
01990   *    program faster.
02000         IF wa_res-txt EQ 'DELETE NEXT RECORD'.
02010   * The record should be deleted for the same reason as the last item
02020           DELETE it_final.
02030           CONTINUE.
02040         ELSE.
02050           wa_final-bldat = wa_res-bldat.
02060         ENDIF.
02070       ENDIF.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i run the jobs for which i got dump individualyy one after other, then the jobs executed successfully.&lt;/P&gt;&lt;P&gt;Pls help me in this regrad.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can i use filed-symbols in thsi case to avoid dump?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance .&lt;/P&gt;&lt;P&gt;Taj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Dec 2008 14:16:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026681#M1169364</guid>
      <dc:creator>former_member213215</dc:creator>
      <dc:date>2008-12-30T14:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: dump during processing on multiple work process.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026682#M1169365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use Package Size with Internal Tables declaration. &lt;/P&gt;&lt;P&gt;Or Send a Mail to your basis with Below lines: &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Runtime errors TSV_TNEW_PAGE_ALLOC_FAILED&lt;/STRONG&gt; &lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;What happened?* &lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;You attempted to extend an internal table, but the required space was&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;not available.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers, &lt;/P&gt;&lt;P&gt;Amit.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Dec 2008 14:20:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026682#M1169365</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-30T14:20:32Z</dc:date>
    </item>
    <item>
      <title>Re: dump during processing on multiple work process.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026683#M1169366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your Internal table contains Huge data(more than 2GB) ..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Dec 2008 14:21:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026683#M1169366</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-30T14:21:07Z</dc:date>
    </item>
    <item>
      <title>Re: dump during processing on multiple work process.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026684#M1169367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's the page allocation problem, try to minimize the background job in report1 or release the jobs batch by batch........ let us say at a time release 10 jobs and once the jobs are completed than release another set of jobs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sasi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Dec 2008 14:23:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026684#M1169367</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-30T14:23:00Z</dc:date>
    </item>
    <item>
      <title>Re: dump during processing on multiple work process.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026685#M1169368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI&lt;/P&gt;&lt;P&gt;It seems memory available to a particular process in your case was not enough to continue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you try to implement the same by convertin Report2 as an FM and calling it as:&lt;/P&gt;&lt;P&gt;CALL FUNCTION func STARTING NEW TASK task &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now instead of making different variants you could just loop over the FM with different values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this does not seem feasible restrict your data anyhow.&lt;/P&gt;&lt;P&gt;Revet with findings!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Dec 2008 14:28:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-during-processing-on-multiple-work-process/m-p/5026685#M1169368</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-30T14:28:20Z</dc:date>
    </item>
  </channel>
</rss>

