Re: Can't get INSERT /*+ APPEND */ to indicate direct load in execution plan.....

From: "Bobak, Mark" <Mark.Bobak_at_proquest.com> To: Greg Rahn <greg_at_structureddata.org>; "oratune_at_yahoo.com" <oratune_at_yahoo.com> Cc: Niall Litchfield <niall.litchfield_at_gmail.com>; "oracle-l_at_freelists.org" <oracle-l_at_freelists.org> Sent: Monday, October 31, 2011 1:29 PM
Subject: RE: Can't get INSERT /*+ APPEND */ to indicate direct load in execution plan.....

I thought about that possibility, but I could find no such limitation documented anywhere.  
Also, I moved from a preprod to a test instance, and it started working.  I’ll need to revisit preprod, to see the difference, but, it is working now, so the problem was not the datatype.  
-Mark
 
From:Greg Rahn [mailto:greg_at_structureddata.org] Sent: Monday, October 31, 2011 4:26 PM
To: oratune_at_yahoo.com
Cc: Bobak, Mark; Niall Litchfield; oracle-l_at_freelists.org Subject: Re: Can't get INSERT /*+ APPEND */ to indicate direct load in execution plan.....  
Incorrect. You don't need either of those to have direct path inserts. 

Could it be related to a restriction the complex data types?

On Oct 31, 2011, at 12:42 PM, David Fitzjarrell <oratune_at_yahoo.com> wrote: parallel_degree_policy              string      MANUAL
>This should be set to AUTO to enable direct path inserts in parallel mode.  Also the session  must have parallel dml enabled:
> 
>alter session enable parallel dml;
> 
>Once those two changes are made you should see direct path enable and displayed in the plan.

--
http://www.freelists.org/webpage/oracle-l