<?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: db file sequential read in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369670#M868337</link>
    <description>Yes, basically there isn't an index on a search field within your query.  Therefore the only way it can perform your query is to scan the whole table.&lt;BR /&gt;&lt;BR /&gt;If this is a required query, you either need to add extra index(es) to you schema, or rewrite the query.</description>
    <pubDate>Wed, 01 Sep 2004 03:22:35 GMT</pubDate>
    <dc:creator>Simon Hargrave</dc:creator>
    <dc:date>2004-09-01T03:22:35Z</dc:date>
    <item>
      <title>db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369669#M868336</link>
      <description>A SQL statment needs a long time to execution. This session often waited for 'db file sequential read'. Can anyone explain this? It means "Full table scan"?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Eric</description>
      <pubDate>Wed, 01 Sep 2004 03:03:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369669#M868336</guid>
      <dc:creator>ericfjchen</dc:creator>
      <dc:date>2004-09-01T03:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369670#M868337</link>
      <description>Yes, basically there isn't an index on a search field within your query.  Therefore the only way it can perform your query is to scan the whole table.&lt;BR /&gt;&lt;BR /&gt;If this is a required query, you either need to add extra index(es) to you schema, or rewrite the query.</description>
      <pubDate>Wed, 01 Sep 2004 03:22:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369670#M868337</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-09-01T03:22:35Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369671#M868338</link>
      <description>If Oracle performs a index scan, the session wait event should be "db file scattered read", right?&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Sep 2004 03:28:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369671#M868338</guid>
      <dc:creator>ericfjchen</dc:creator>
      <dc:date>2004-09-01T03:28:46Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369672#M868339</link>
      <description>The wait event 'db file sequential read' can have all kind of explanations. The most important thing is to read it's context. I have the same wait events, but in the context of the complete performance it means nothing.</description>
      <pubDate>Wed, 01 Sep 2004 04:09:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369672#M868339</guid>
      <dc:creator>Marcel Boogert_1</dc:creator>
      <dc:date>2004-09-01T04:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369673#M868340</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;db file sequential read is due to INDEXED reads and  it is single block IO. It is not the result of a full scan.&lt;BR /&gt;&lt;BR /&gt;Also, a sequential read is usually a single-block read, although it is possible to see sequential reads for more than one block.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hope this helps!&lt;BR /&gt;regards&lt;BR /&gt;Yogeeraj</description>
      <pubDate>Wed, 01 Sep 2004 08:43:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369673#M868340</guid>
      <dc:creator>Yogeeraj_1</dc:creator>
      <dc:date>2004-09-01T08:43:52Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369674#M868341</link>
      <description>Hi ALL,&lt;BR /&gt;&lt;BR /&gt;Thanks for your reply in advance.&lt;BR /&gt;However, I am very confused whether it is full scan or not. Does any Oracle white paper mention this? Could you pls explain detail about 'sequential'? When that session execution, v$session_wait also showed P1, P2, and P3.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    P1 = file#&lt;BR /&gt;    P2 = block#&lt;BR /&gt;    P3 = blocks&lt;BR /&gt;&lt;BR /&gt;After checking this, it is a table.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Eric</description>
      <pubDate>Wed, 01 Sep 2004 19:52:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369674#M868341</guid>
      <dc:creator>ericfjchen</dc:creator>
      <dc:date>2004-09-01T19:52:58Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369675#M868342</link>
      <description>It is NOT a full scan (contrary to the name).&lt;BR /&gt;There are LOTs of writings in this subject.&lt;BR /&gt;CHeck Oracle sites, and hotsos, and ixora,...&lt;BR /&gt;&lt;BR /&gt;For example.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:3230221064491" target="_blank"&gt;http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:3230221064491&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.hotsos.com/dnloads/1/kevents/db_file_sequential_read.html" target="_blank"&gt;http://www.hotsos.com/dnloads/1/kevents/db_file_sequential_read.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Sep 2004 23:58:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369675#M868342</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2004-09-01T23:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369676#M868343</link>
      <description>Hi Eric,&lt;BR /&gt;Check this documment.&lt;BR /&gt;&lt;BR /&gt;E.</description>
      <pubDate>Fri, 03 Sep 2004 11:04:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369676#M868343</guid>
      <dc:creator>Emilio Brusa</dc:creator>
      <dc:date>2004-09-03T11:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: db file sequential read</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369677#M868344</link>
      <description>Eric,&lt;BR /&gt;&lt;BR /&gt;DB Sequential Read doesn't nessecarily mean that a FTS scan is being done, only that it is pulling multiple blocks from the database in a query.  DB Scattered Read means that it is most likely using an index.  I would recommend checking the SQL plan for the query that you see it on, and see what it is doing.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Brian</description>
      <pubDate>Fri, 03 Sep 2004 15:22:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/db-file-sequential-read/m-p/3369677#M868344</guid>
      <dc:creator>Brian Crabtree</dc:creator>
      <dc:date>2004-09-03T15:22:12Z</dc:date>
    </item>
  </channel>
</rss>

