Re: "direct path read" and "db file sequential read" used for full table scans in 11g
From: Sayan Malakshinov <xt.and.r_at_gmail.com>
Date: Fri, 31 Aug 2012 02:23:01 +0400
Message-ID: <CAOVevU5iW3b3ynJPGWfF+HmPsmVmFOu7G7Nw7HgNinw+r+7xEw_at_mail.gmail.com>
About 1: have you tried to decrease _small_table_threshold? What size of your tables on which you testing?
About 2: have you tried to flush buffer_cache?
Date: Fri, 31 Aug 2012 02:23:01 +0400
Message-ID: <CAOVevU5iW3b3ynJPGWfF+HmPsmVmFOu7G7Nw7HgNinw+r+7xEw_at_mail.gmail.com>
About 1: have you tried to decrease _small_table_threshold? What size of your tables on which you testing?
About 2: have you tried to flush buffer_cache?
On Fri, Aug 31, 2012 at 1:47 AM, Allen, Brandon
<Brandon.Allen_at_oneneck.com> wrote:
> Question #3 is open again
> According to the docs the answer I thought I'd found would only explain what I'm seeing if I had the parameter parallel_degree_policy=AUTO, but I just checked and it is set to MANUAL, so the parallel queries should still be using direct path reads according to the doc: http://docs.oracle.com/cd/E11882_01/server.112/e25513/initparams179.htm#REFRN10310
>
> SQL> show parameter PARALLEL_DEGREE_POLICY
>
> NAME TYPE VALUE
> ------------------------------------ ----------- ------
> parallel_degree_policy string MANUAL
>
-- Best regards, Sayan Malakshinov Senior oracle developer PromSvayzBank Tel: +7 903 207-1576 -- http://www.freelists.org/webpage/oracle-lReceived on Thu Aug 30 2012 - 17:23:01 CDT