I just RTFM a little and if you truncate a partition and the table have a global index it will become unusable. Yechiel Adar Mehish Computer Services ----- Original Message ----- From: "Niall Litchfield" <niall.litchfield@xxxxxxxxx> To: <jdunn@xxxxxxxxx> Cc: "Mark J. Bobak" <mark@xxxxxxxxx>; <Oracle-L@xxxxxxxxxxxxx> Sent: Thursday, January 20, 2005 5:23 PM Subject: Re: ORA-26028: index initially in unusable state > On Thu, 20 Jan 2005 14:17:49 -0000, John Dunn <jdunn@xxxxxxxxx> wrote: > > > > <<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>> > > > > Thnaks for your comments, but rebuilding the indexes takes far longer than > > the time saved during the load, even with nologging! > > > > And it is still not clear to me what causes the index to become unusuable. > > Maybe I'm all at sea here, but my understanding is that the index is > already marked UNUSABLE before the load starts. The error message is > telling you that you can't do the load because maintaining the index > is not possible because of the existing state of the index. > > > > -- > Niall Litchfield > Oracle DBA > http://www.niall.litchfield.dial.pipex.com > -- > //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l