<?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 Indexing issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/indexing-issue/m-p/3300117#M789972</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       I have problem with indexing , iam writing an extractor for pulling data into BI .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where we are using one ztable .&lt;/P&gt;&lt;P&gt;as we ran the extractor we faced some performance issue .so i checked with the ztable its taking longer time ..&lt;/P&gt;&lt;P&gt;so i checked for the index where i found as in the below ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Index does not exist in database system ORACLE"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;even now iam facing the same problem of system time out&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DUMP ANALYSIS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; After a specific time, the program is terminated to make the work area&lt;/P&gt;&lt;P&gt; available to other users who may be waiting.&lt;/P&gt;&lt;P&gt; This is to prevent a work area being blocked unnecessarily long by, for&lt;/P&gt;&lt;P&gt; example:&lt;/P&gt;&lt;P&gt; - Endless loops (DO, WHILE, ...),&lt;/P&gt;&lt;P&gt; - Database accesses with a large result set&lt;/P&gt;&lt;P&gt; - Database accesses without a suitable index (full table scan)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The maximum runtime of a program is limited by the system profile&lt;/P&gt;&lt;P&gt; parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this&lt;/P&gt;&lt;P&gt;  time limit is&lt;/P&gt;&lt;P&gt; exceeded, the system attempts to cancel any running SQL statement or&lt;/P&gt;&lt;P&gt; signals the ABAP processor to stop the running program. Then the system&lt;/P&gt;&lt;P&gt; waits another 60 seconds maximum. If the program is then still active,&lt;/P&gt;&lt;P&gt; the work process is restarted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;vinay.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Jan 2008 05:57:47 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-24T05:57:47Z</dc:date>
    <item>
      <title>Indexing issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/indexing-issue/m-p/3300117#M789972</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       I have problem with indexing , iam writing an extractor for pulling data into BI .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where we are using one ztable .&lt;/P&gt;&lt;P&gt;as we ran the extractor we faced some performance issue .so i checked with the ztable its taking longer time ..&lt;/P&gt;&lt;P&gt;so i checked for the index where i found as in the below ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Index does not exist in database system ORACLE"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;even now iam facing the same problem of system time out&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DUMP ANALYSIS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; After a specific time, the program is terminated to make the work area&lt;/P&gt;&lt;P&gt; available to other users who may be waiting.&lt;/P&gt;&lt;P&gt; This is to prevent a work area being blocked unnecessarily long by, for&lt;/P&gt;&lt;P&gt; example:&lt;/P&gt;&lt;P&gt; - Endless loops (DO, WHILE, ...),&lt;/P&gt;&lt;P&gt; - Database accesses with a large result set&lt;/P&gt;&lt;P&gt; - Database accesses without a suitable index (full table scan)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The maximum runtime of a program is limited by the system profile&lt;/P&gt;&lt;P&gt; parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this&lt;/P&gt;&lt;P&gt;  time limit is&lt;/P&gt;&lt;P&gt; exceeded, the system attempts to cancel any running SQL statement or&lt;/P&gt;&lt;P&gt; signals the ABAP processor to stop the running program. Then the system&lt;/P&gt;&lt;P&gt; waits another 60 seconds maximum. If the program is then still active,&lt;/P&gt;&lt;P&gt; the work process is restarted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;vinay.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2008 05:57:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/indexing-issue/m-p/3300117#M789972</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-24T05:57:47Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/indexing-issue/m-p/3300118#M789973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vinay, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer this link,&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3723358411d1829f0000e829fbfe/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3723358411d1829f0000e829fbfe/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;kindly reward if found helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers,&lt;/P&gt;&lt;P&gt;Hema.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jan 2008 04:19:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/indexing-issue/m-p/3300118#M789973</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-25T04:19:32Z</dc:date>
    </item>
  </channel>
</rss>

