Re: Partitioned Explain Plan - Pstart/Pstop = KEY after execution

From: Mohamed Houri <mohamed.houri_at_gmail.com>
Date: Thu, 6 Jun 2013 17:26:15 +0200
Message-ID: <CAJu8R6gUD5D54EjUNM8SdAoiFzgL+OzKzJWA4GD_U9ED=Ag5uw_at_mail.gmail.com>

The partition pruning did occur in this case. This is just an indication that during the parse time the optimizer couldn't know what is the exact partition to prune. This happens when you are using partition keys as bind variable
Best regards

Mohamed Houri
www.hourim.wordpress.com

2013/6/6 <Christopher.Taylor2_at_parallon.net>

> Env: 10.2.0.4 RAC Linux 64-bit
> I've got an explain plan with Pstart/Pstop with "KEY" instead of partition
> numbers. I've been reading
> http://www.oracle.com/technetwork/database/bi-datawarehousing/twp-explain-the-explain-plan-052011-393674.pdf(The Oracle Optimizer Explain the Explain Plan) and it explains that KEY is
> used when Oracle believes the execution will dynamically partition prune.
>
> So I executed my statement and traced it (of course) and still the explain
> plan shows KEY KEY and running it through orasrp shows that many partitions
> were scanned (perhaps not all of them however - I haven't checked).
>
> So, is it safe to say that *after* execution if the plan has KEY KEY then
> partition pruning did not occur?
>
> Thanks!!
>
> Chris Taylor
> Oracle DBA
> Parallon IT&S
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Bien Respectueusement
Mohamed Houri


--
http://www.freelists.org/webpage/oracle-l

Received on Thu Jun 06 2013 - 17:26:15 CEST