My Oracle Support Banner

How To Have A Single Range Column Partition With Hashed Subpartitions (Doc ID 863699.1)

Last updated on FEBRUARY 01, 2022

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1 to 11.2]
Information in this document applies to any platform.
This is an "HOW TO" style article and as such will work on all supported versions.
This was tested against Oracle RDBMS


NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

The following requirement for a Partitioned table has been implemented and tested.  The requirement states:

"A large partitioned table requires all negative values to be in a single partition for column  NUM_COL, and the positive values to be in another partition which requires hashed sub-partitions.  Thus allowing the efficient storage and accessibility of the positive values for future SQL queries."

One of the questions that requires answering here during the partition design phase is number of  sub-partitions required in the positive number partition.  This is important as a future redesign of this table with large amounts of data will be a large task.  An example of the possible formula to use for this is:

# subpartitions = (# rows_in_table) / (desired #rows per subpartition)

NOTE.   Here the #rows_in_table is defined as the positive numbers as we are not interested in the negative values.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.