Partitioning FAQs

* Partitioned indexes with direct path SQL loader
When skip_index_maintenance option is used, index partitions that have data loaded into
will be set to unusable. Partitions that do not have new data loaded will remain usable.
skip_index_maintenance option is only valid with direct path load.

* How do I convert a partitoned table into a non partitioned table?
1. Export/import
2. Insert into non partitioned table select from partitioned table
3. Alter table exchange partition with table

* How do I add a subpartition to a simple partitioned table?
Not possible. You add subpartition to a composite-potitioned table.
You can not change a simple partitioned table into a
composite-partitioned table this way. Easiest way is to create a new
composite-partitioned table and then insert into that new table select
from the old table.

* What are differences between non partitioned indexes and global indexes?
Non partitioned indexes are treated as global indexes. Global indexes can be partitioned 
or non partitioned.

* How many partitions should I create? What's the limit?
(64k-1) is the maximum # of partitions/subpartitions you can create for a table.
Practically, 1000 partitions has been tested. When a query is compiled about a table,
metadata information is loaded into the metadata cache (in SGA) and also into the cursor.
So, while 64k-1 is the theoretical limit, there may be physical limitations
well before that.