Partition Pruning Min/Max Optimization Fails when Parallel Query Run in Serial
(Doc ID 1941770.1)
Last updated on FEBRUARY 17, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle 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.
Query execution takes very long time when there is no local index on the partition column and it was going for full table scan.
Review trace file generated by event 10128.
Compare to running the same but with no_parallel instead of parallel.
If a select query with,
1. range partitioned table
2. uses MIN/MAX operator on partitioned key
3. iterator uses MIn/MAX optimization
PARTITION RANGE ALL MIN/MAX
4. parallel query plan is run in serial
5. all of the partitions are accessed
then you might be encountering this issue.
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