Rebuild or Re-Create Local Partitioned Bitmap Indexes?
624104Feb 10 2009 — edited Feb 10 2009Hi all,
I have been looking around for some help on this scenario but I cannot find one with the issue that I am pondering, so I am coming to the gurus.
Let's say I have a data warehouse with a partitioned (by quarter) fact table that uses local partitioned bitmap indexes. I wish to disable the bitmap indexes (either by dropping or marking it unusable) during a batch ETL process but was unsure what the best way to do it is.
Here's where the problem comes in, with local partitioned bitmap indexes, when I add a partition to the fact table, Oracle will automatically add partitions to the local bitmap indexes to support them. That's great but my problem is if I drop the the indexes before a mass insert and re-create them again, it looks like the only way to associate the partitions on the fact table to the index is to explicitly call the partitions on the fact when re-creating the index. Am I wrong here? Is there a way to create a local partitioned bitmap on an already-partitioned table and automatically associate the existing ones to the bitmap index? Meaning if I have a table partitioned (part1, part2, part3, etc), is there a way to automatically partition the index with part1,part2, part3, etc?
Or is marking a bitmap index unusable good enough to allow for better performing inserts in a data warehouse?
Thanks for anyone's input!
-TimS