Parallel Plan Runs Serially even after Patching for Bug 17423234 when MIN/MAX Operator on Partitioning Key (Doc ID 1953737.1)

Last updated on DECEMBER 12, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

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):

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms