Re: Can t get INSERT /*+ APPEND */ to indicate direct load in execution plan
From: Greg Rahn <greg_at_structureddata.org>
Date: Fri, 4 Nov 2011 11:29:08 -0700
Message-ID: <CAGXkmiuVmPMOALC0OyiFDO3dpKsV4mKUf-Nn=O7b23V3PagKZQ_at_mail.gmail.com>
Shouldn't be a big surprise, but bugs that don't get filed, don't get addressed.
Date: Fri, 4 Nov 2011 11:29:08 -0700
Message-ID: <CAGXkmiuVmPMOALC0OyiFDO3dpKsV4mKUf-Nn=O7b23V3PagKZQ_at_mail.gmail.com>
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-constraints-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-lReceived on Fri Nov 04 2011 - 13:29:08 CDT