<?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: Memory analysis for background job in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156569#M1194566</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chinmay,&lt;/P&gt;&lt;P&gt;                The tcode for memory analysis is  S_MEMORY_INSPECTOR.You can logon to this tcode.I think it might help you to solve your query.&lt;/P&gt;&lt;P&gt;Have a best day ahead.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Feb 2009 13:27:13 GMT</pubDate>
    <dc:creator>gaursri</dc:creator>
    <dc:date>2009-02-04T13:27:13Z</dc:date>
    <item>
      <title>Memory analysis for background job</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156567#M1194564</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 a report which when run as background job, gives a runtime dump due to memory overflow.&lt;/P&gt;&lt;P&gt;It seems the there is some internal table having many entries hence consuming ABAP memory, but we could not find which one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simillar to runtime analysis (SE30), is there any tool to monitor the memory consumption according to internal tables? I had heard of some "memory inspector" simillar to code inspector, how to use it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we tried analysing memory space taken by internal tables during debugging, but it runs for very long period, and has many internal tables, so, it is taking long to analyse.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please suggest some tool to monitor the memory consumption while the report is running in background.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Feb 2009 10:23:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156567#M1194564</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-04T10:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: Memory analysis for background job</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156568#M1194565</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;It might would happened due to a loop which might have gone into infinite loop ......&lt;/P&gt;&lt;P&gt;so if u are looping into a internal table just loop it properly and go for debugging at every point you are &lt;/P&gt;&lt;P&gt;looping at.you will find where it is going into dump.&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Feb 2009 10:30:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156568#M1194565</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-04T10:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: Memory analysis for background job</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156569#M1194566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chinmay,&lt;/P&gt;&lt;P&gt;                The tcode for memory analysis is  S_MEMORY_INSPECTOR.You can logon to this tcode.I think it might help you to solve your query.&lt;/P&gt;&lt;P&gt;Have a best day ahead.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Feb 2009 13:27:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156569#M1194566</guid>
      <dc:creator>gaursri</dc:creator>
      <dc:date>2009-02-04T13:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: Memory analysis for background job</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156570#M1194567</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;Is it your own code? If so: in your batch job you can create memory snapshots with the following method call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CL_ABAP_MEMORY_UTILITIES=&amp;gt;WRITE_MEMORY_CONSUMPTION_FILE( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure that you don't call this method in a loop. Only make single calls at important&lt;/P&gt;&lt;P&gt;POI (points of interest). E.g. after selection... ... . Each call will write a file to the application&lt;/P&gt;&lt;P&gt;server that can be analyzed with transation S_MEMORY_INSPECTOR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it is SAP standard code you can use the debugger and create snapshots with the Services of&lt;/P&gt;&lt;P&gt;the Memory Analysis tool. These can be analyzed with S_MEMOY_INSPECTOR as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hermann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Feb 2009 14:51:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/memory-analysis-for-background-job/m-p/5156570#M1194567</guid>
      <dc:creator>HermannGahm</dc:creator>
      <dc:date>2009-02-04T14:51:52Z</dc:date>
    </item>
  </channel>
</rss>

