RE: Index in unusable mode during direct load w/ singlerow
- From: "Eric Buddelmeijer" <Eric.Buddelmeijer@xxxxxxxxxx>
- To: <jmao@xxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Sat, 5 Nov 2005 09:42:11 +0100
Hi Jessica,
I don't know much about sqlloader. I do know you could prevent this from
happening by loading into a separate table, build the necessary indexes and
then do a partition exchange from the 'work' table to the partitioned table.
Nobody notices you are loading until you do the partition exchange and that
is a 5 second operation as it involves only dictionary updates.
Eric
-----Oorspronkelijk bericht-----
Van: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
Namens Jessica Mao
Verzonden: vrijdag 4 november 2005 20:05
Aan: oracle-l@xxxxxxxxxxxxx
Onderwerp: Index in unusable mode during direct load w/ singlerow
Hi,
We have a range partitioned table, there's sqlldr running in direct mode w/
SINGLEROW option on 1 of the partitions, meanwhile there's a procedure who
queries the table using the partition key as the only predicate. Every once
in a while, we get an ora-1502 "index '%s.%s' or partition of such index is
in unusable state". I thought using SINGLEROW should avoid such error?
The db is 9.2.0.6. happens on both hp and sun platform.
Thanks! -Jessica
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
