Re: Can't get INSERT /*+ APPEND */ to indicate direct load in execution plan.....
Date: Wed, 2 Nov 2011 08:38:43 +0100
could you please clarify the following:
>> It's still using PX ...
Yes, I see that parallel execution is involved.
I wanted to know if the *insert* part of the statement was executed in parallel and where is the evidence for that. I believe that only the select part execution mode is visible in the plan output, but I may be wrong, of course.
My point was that as far as Mark's first mail is concerned, we see that conventional load is used, but we can only guess if the insert into table TEST is in serial mode or not, am I missing something?
On Wed, Nov 2, 2011 at 7:58 AM, Greg Rahn <greg_at_structureddata.org> wrote:
> The reason you see the NO_PARALLEL in the outline because you have not
> calibrated your IO for auto DOP to work as shown by the Notes section.
> After doing so you should see the SHARED directive show up in its
> place. It's still using PX and you can see this from looking at
> v$pq_tqstat from the same session you ran the query. One can also
> look at the SQL Monitor Report as well.
> Using scott.emp might be a poor example because there is only 1
> granule for the table scan so only 1 PX server gets work.
> On Tue, Nov 1, 2011 at 2:45 PM, Radoulov, Dimitre <cichomitiko_at_gmail.com> wrote:
>> Hi Mark,
>> yes, the documentation is clear.
>> Actually I should have said: the append hint was ignored (not *only*
>> the append hint was ignored).
>> I mean that, if I'm reading this correctly, the plan output alone is not
>> sufficient to determine if the table TEST
>> is accessed in parallel or only the table CS_CONTENT_XML_DATA is read in
>> With a simple test I'm getting the following output:
>> insert into emp_1 select /*+ parallel */ * from scott.emp
>> Outline Data
>> FULL(_at_"INS$1" "EMP_1"@"INS$1")
>> FULL(_at_"SEL$1" "EMP"@"SEL$1")
>> - automatic DOP: skipped because of IO calibrate statistics are missing
> Greg Rahn