do you have unique and pk indexes? those cause more I/O since you have to do a lookup for each row loaded? Your 'sequential' wait leads me to believe this.
I don't think your IO increase has anything to do with partitioning. It may have to do with loading data out of synch with your clustering factor. This could cause increased index maintenance, higher waits, and higher IO.
- Original message --------------
> No, no triggers. I believe the high I/O is due to index maintenance.
> When I remove the indexes or run the load with direct path, the load
> screams. Thx!
>
>
> Mark
>
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Oct 11 2004 - 12:02:37 CDT
