| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Maximum number of partitions?
The feature that 10g does change, though is the numbering strategy. Internal numbering is no longer goes: 1,2,3,4..., instead it starts life with increments of 10.
Consequently, since the external numbering uses analytic functions (row_number, IIRC) to generate a sequence number, the cost of dropping, splitting, merging, coalescing, or otherwise doing partition maintenance is largely eliminated.
(e.g. no more renumbering of every partition and its index segments when you drop the bottom partition of a table - Oracle just doesn't bother).
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/seminar.html Optimising Oracle Seminar - schedule updated July 14th
The 10g Reference Guide, although it might be outdated, still says:
"Maximum number of partitions allowed per table or index: 64 KB - 1 partitions"
Actually I wonder how the scientists in Oracle have managed to create an entirely new measurement unit for partition counts: KB e.g. KelvinByte? How can you actually substract one "partition" from an amount of information at specific temperature?
Or has 10g adapted a new, informational-temperatural model instead of the old object-relational one?
Tanel.
 |
 |