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

On Fri, Nov 4, 2011 at 11:45 AM, Bobak, Mark <Mark.Bobak_at_proquest.com> wrote:
> Greg,
>
> Don't suppose you could make that publicly visible?
>
> Thanks,
>
> -Mark
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Greg Rahn
> Sent: Friday, November 04, 2011 2:29 PM
> To: info_at_www.sqltools-plusplus.org
> Cc: oracle-l_at_freelists.org
> Subject: Re: Can t get INSERT /*+ APPEND */ to indicate direct load in execution plan
>
> Shouldn't be a big surprise, but bugs that don't get filed, don't get addressed.
>
> Now there is one -- bug 13347906.
> :-)
>
> On Wed, Nov 2, 2011 at 9:09 AM, Randolf Geist <info_at_www.sqltools-plusplus.org> wrote:
>> The direct-path insert restriction with the non-unique index used to be there up to 10.2. It's no longer there in 11.1 and 11.2, however the change introduced another subtle (and nasty) questionable behaviour, see here:
>>
>> http://oracle-randolf.blogspot.com/2008/11/primary-key-unique-constrai
>> nts-enforced.html
>>
>> It looks like this potential bug hasn't been addressed yet.
>>
>> Randolf
>
> --
> Regards,
> Greg Rahn
> http://structureddata.org
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
>

-- 
Regards,
Greg Rahn
http://structureddata.org
--
http://www.freelists.org/webpage/oracle-l