Re: Perhaps a _REALLY_ dumb question from an experienced dba?

From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Sat, 10 Aug 2013 16:24:50 +0100
Message-ID: <CAMHX9J+Kr+1g5xHm38PzhEmg53wgqUaBWHX8u8OkTq8wsMrO4Q_at_mail.gmail.com>

Here are 2 of my hacking session videos about SQL execution phases, related OPI calls etc, which may be of interest: http://enkitec.tv/2013/03/13/tanel-poders-hacking-session-how-oracle-sql-plans-are-really-executed-part-1/ http://enkitec.tv/2013/03/14/tanel-poders-hacking-session-how-oracle-sql-plans-are-really-executed-part-2/

-- 
*Tanel Poder*
Enkitec (The Exadata Experts)
Training <http://blog.tanelpoder.com/seminar/> |
Troubleshooting<http://blog.tanelpoder.com/>
 | Exadata<http://www.amazon.com/Expert-Oracle-Exadata-Apress/dp/1430233923>
 | Voicee App <http://voic.ee/>



On Thu, Aug 8, 2013 at 9:17 PM, Jonathan Lewis
<jonathan_at_jlcomp.demon.co.uk>wrote:



>

>

>

> Looks like the Cartesian merge join was the real killer - a huge amount of

> CPU to build a massive data set that you eliminated (relatively) quickly by

> passing it through some hash tables.

>

> Then the ranking window sort required you to generate all the data before

> returning the first row.

>

>

>

>



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

Received on Sat Aug 10 2013 - 17:24:50 CEST