Re: Can t get INSERT /*+ APPEND */ to indicate direct load in execution plan
Date: Wed, 2 Nov 2011 10:03:45 -0700 (PDT)
To me what is unsettling is having an enabled constraint with an unusable index; one would expect if the index is unusable the constraint would be invalid.
From: "Bobak, Mark" <Mark.Bobak_at_proquest.com> To: "info_at_www.sqltools-plusplus.org" <info_at_www.sqltools-plusplus.org>; "oracle-l_at_freelists.org" <oracle-l_at_freelists.org> Sent: Wednesday, November 2, 2011 9:49 AM Subject: RE: Can t get INSERT /*+ APPEND */ to indicate direct load in execution plan
Understood....it's just a bit unsettling that you can have an *enabled* constraint, and still get duplicate data into the table.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Randolf Geist Sent: Wednesday, November 02, 2011 12:42 PM To: oracle-l_at_freelists.org
Subject: Re: Can t get INSERT /*+ APPEND */ to indicate direct load in execution plan
good question - it's quite a while ago - and I think to remember since this was not part of a client's problem I didn't open a SR.
Note though that the duplicates are only possible when the non-unique index supporting the PK is in unusable state. Under normal circumstances everything is fine.
> Wow, that's a nasty one, Randolf.
> Did you open SR with Oracle on this?
> If so, what did they say?
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Wed Nov 02 2011 - 12:03:45 CDT