<?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: Shared Memory Space issue in Background Prog execution in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/shared-memory-space-issue-in-background-prog-execution/m-p/5958076#M1337215</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Suresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In memory consumstion lot of things matter it is not just the size of data. I have fetched 60 ~ 70 Million of data in background successfully. May be you need to check following things:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Code optimization&lt;/P&gt;&lt;P&gt;2. Memory settings of SAP server&lt;/P&gt;&lt;P&gt;3. How the selected data is stored&lt;/P&gt;&lt;P&gt;4. Most important the hardware configuration you are using&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At least in background job it doesn't matter how big data you are selecting as long as above parameters are propperly tunned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is lot to explore in SAP! Enjoy SAP!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Augustin.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Aug 2009 05:46:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-08-10T05:46:28Z</dc:date>
    <item>
      <title>Shared Memory Space issue in Background Prog execution</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shared-memory-space-issue-in-background-prog-execution/m-p/5958074#M1337213</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;A program to determine YTD was scheduled to run in back ground.  &lt;/P&gt;&lt;P&gt;Since the program is processing huge volume of data, the Job fails because of the shortage of shared memory space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Solution developed:&lt;/P&gt;&lt;P&gt;We split the data into two slice and create another program to handle it.&lt;/P&gt;&lt;P&gt;i.e. previosly some 10M records were processed by a program. Instead 5M will be processed by existing prg and rest by new prg.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Question:&lt;/P&gt;&lt;P&gt;We are going to schedule the two program at the same time. Theoritically, its once again going to consume same memory. Will this once again result in shortage of memory space if we run it in parallel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Suresh Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Aug 2009 04:39:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shared-memory-space-issue-in-background-prog-execution/m-p/5958074#M1337213</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-10T04:39:11Z</dc:date>
    </item>
    <item>
      <title>Re: Shared Memory Space issue in Background Prog execution</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shared-memory-space-issue-in-background-prog-execution/m-p/5958075#M1337214</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;If you are again trying to run both the programs parallely which access the same combination of tables , as you said it will consume the same amount of memory which might again fail. Its better to schedule the two programs in sequence such that the 2nd prog is run after the completion of the first program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Aug 2009 04:43:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shared-memory-space-issue-in-background-prog-execution/m-p/5958075#M1337214</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-10T04:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: Shared Memory Space issue in Background Prog execution</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shared-memory-space-issue-in-background-prog-execution/m-p/5958076#M1337215</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Suresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In memory consumstion lot of things matter it is not just the size of data. I have fetched 60 ~ 70 Million of data in background successfully. May be you need to check following things:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Code optimization&lt;/P&gt;&lt;P&gt;2. Memory settings of SAP server&lt;/P&gt;&lt;P&gt;3. How the selected data is stored&lt;/P&gt;&lt;P&gt;4. Most important the hardware configuration you are using&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At least in background job it doesn't matter how big data you are selecting as long as above parameters are propperly tunned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is lot to explore in SAP! Enjoy SAP!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Augustin.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Aug 2009 05:46:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shared-memory-space-issue-in-background-prog-execution/m-p/5958076#M1337215</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-10T05:46:28Z</dc:date>
    </item>
  </channel>
</rss>

