PARTITION_COUNT Shows Large Value 1048575 With Interval Partitioning
(Doc ID 1447928.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.6 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
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.
- In case of Interval Partitioning, the value of the column PARTITION_COUNT in ALL|DBA|USER_part_tablesis very high1048575even though the actual number partitions created are much less in number.
Consider the scenario below:
- Pstop value in an execution plan against the interval partitioned table where no partition pruning takes place also shows the 1048575 value.
-------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| <strong>Pstop</strong> | -------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 13 | 2 (0)| 00:00:01 | | | | 1 | PARTITION RANGE ALL| | 1 | 13 | 2 (0)| 00:00:01 | 1 |<strong>1048575</strong>| | 2 | TABLE ACCESS FULL | T1 | 1 | 13 | 2 (0)| 00:00:01 | 1 |<strong>1048575</strong>| --------------------------------------------------------------------------------------------
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |