Re: ORA-26028: index initially in unusable state

I think the idea is to skip unusable indexes, do the load, then rebuild the indexes w/ NOLOGGING. If you rebuild the index before the load, the index maintenance will cause significant logging. It's faster and more efficient to load while indexes are unusable. -Mark

On Thu, 2005-01-20 at 07:43, Niall Litchfield wrote:

> On Thu, 20 Jan 2005 11:56:31 -0000, John Dunn <jdunn_at_sefas.com> wrote:
> > I am trying to understand why I get this error when using direct path
> > sqlldr.
> >
> > There are no constraints on the table, just this index which is one field in
> > the table.
> >
> > Why do I get this error?.
> >
> > The error text says
> >
> > Either rebuild the index, re-create the index, or use either
> > SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).
> >
> > but it is not clear to me which I should do. using the skip options seems
> > easiest, but what are the implications of using any of the skip options?
>
> The implications are that the index will remain unusable, but the data
> will get loaded.
>
> I'm not sure I see how ALTER INDEX REBUILD is particularly hard, do
> you want the index to remain unusable and if so why do you not just
> drop it?

--
Mark J. Bobak
mark_at_bobak.net
"Science is the belief in the ignorance of experts."  --Richard P.
Feynman


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