My Oracle Support Banner

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 11.2.0.1 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.

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.

Query execution takes very long time when there is no local index on the partition column and it was going for full table scan.

Test Case

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.

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
Cause
Solution
References

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