Re: Can t get INSERT /*+ APPEND */ to indicate direct load in execution plan
Date: Wed, 02 Nov 2011 18:12:38 +0100
The expected behaviour can be seen when using conventional inserts - it errors out saying that the index supporting the constraint is in unusable state hence the insert isn't possible.
Having the index in unusable state doesn't mean that the constraint is invalid, because the data entered so far is still ensured to be unique.
You could even have a unique / PK constraint in validated but disabled state. This way no supporting index is required / generated, but again no DML against the table is possible. Still the data in the table will be valid with regard to the constraint.
> 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.
> David Fitzjarrell