Parallel Plan Runs Serially even after Patching for Bug 17423234 when MIN/MAX Operator on Partitioning Key
(Doc ID 1953737.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 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.
Even after applying the patch for unpublished Bug 17423234 - PARTITION PRUNING MIN/MAX OPTIMIZATION FAILS WHEN PARALLEL PLAN RUN IN SERIAL, a parallel plan still runs serially when there is a MIN/MAX operator on the partitioning key.
Example: This query executes the parallel plan serially (no slaves allocated):
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