<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Striving for Optimal Performance &#187; 11gR1</title>
	<atom:link href="http://antognini.ch/category/oracledatabase/11gr1/feed/" rel="self" type="application/rss+xml" />
	<link>http://antognini.ch</link>
	<description></description>
	<lastBuildDate>Thu, 02 Sep 2010 04:05:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Partition-Wise Join of List-Partitioned Tables</title>
		<link>http://antognini.ch/2010/08/partition-wise-join-of-list-partitioned-tables/</link>
		<comments>http://antognini.ch/2010/08/partition-wise-join-of-list-partitioned-tables/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 09:59:08 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR1]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Partitioning]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1202</guid>
		<description><![CDATA[When two tables are equi-partitioned on their join keys, the query optimizer is able to take advantage of partition-wise joins. To make sure that the tables are equi-partitioned, as of Oracle Database 11g reference partitioning can be used. In fact, per definition, with reference partitioning all “related” tables have exactly the same partitioning schema. If [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/08/partition-wise-join-of-list-partitioned-tables/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Evolution of a SQL Plan Baseline Based on a DELETE Statement</title>
		<link>http://antognini.ch/2010/06/evolution-of-a-sql-plan-baseline-based-on-a-delete-statement/</link>
		<comments>http://antognini.ch/2010/06/evolution-of-a-sql-plan-baseline-based-on-a-delete-statement/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 14:21:26 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Query Optimizer]]></category>
		<category><![CDATA[SQL Trace]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1139</guid>
		<description><![CDATA[During an evolution the database engine compares the performance of two execution plans. The aim is to find out which one provides the better performance. For that purpose it has to run the SQL statement on which the SQL plan baseline is based and compare some execution statistics. The following output of the DBMS_SPM.EVOLVE_SQL_PLAN_BASELINE function [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/06/evolution-of-a-sql-plan-baseline-based-on-a-delete-statement/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Optimizer Mode Mismatch Does Not Prevent Sharing of Child Cursor!?!?</title>
		<link>http://antognini.ch/2010/06/optimizer-mode-mismatch-does-not-prevent-sharing-of-child-cursor/</link>
		<comments>http://antognini.ch/2010/06/optimizer-mode-mismatch-does-not-prevent-sharing-of-child-cursor/#comments</comments>
		<pubDate>Thu, 03 Jun 2010 17:40:03 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR1]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[9iR2]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[Query Optimizer]]></category>
		<category><![CDATA[SQL Trace]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1113</guid>
		<description><![CDATA[The aim of this post is to describe a strange (buggy) situation that I observed recently. But before doing that, I shortly summarize what a parent cursor and a child cursor are as well as when they can be shared. By the way, I borrowed this description from the pages 20/21 of my book. Hence, [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/06/optimizer-mode-mismatch-does-not-prevent-sharing-of-child-cursor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Exadata Storage Server and the Query Optimizer &#8211; Part 3</title>
		<link>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-part-3/</link>
		<comments>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-part-3/#comments</comments>
		<pubDate>Wed, 05 May 2010 14:55:26 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Exadata]]></category>
		<category><![CDATA[Parallel Processing]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1018</guid>
		<description><![CDATA[In the first and second post of this series I shared with you some basics about smart scan and gave some details about projection and restriction. The aim of this post is to cover the third basic technique: join filtering.
Join filtering is not something specific to the Exadata Storage Server. In fact, it is an [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-part-3/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Exadata Storage Server and the Query Optimizer – Part 2</title>
		<link>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-%e2%80%93-part-2/</link>
		<comments>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-%e2%80%93-part-2/#comments</comments>
		<pubDate>Mon, 03 May 2010 05:48:16 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Exadata]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1016</guid>
		<description><![CDATA[In the first post of this series I shared with you some basics about smart scan and gave some details about projection. The aim of this post is to cover the second basic technique: restriction. Simply put, the aim of this technique is to offload to a cell the processing of predicates found in the [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-%e2%80%93-part-2/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Bind Variable Peeking: Bane or Boon?</title>
		<link>http://antognini.ch/2010/04/bind-variable-peeking-bane-or-boon/</link>
		<comments>http://antognini.ch/2010/04/bind-variable-peeking-bane-or-boon/#comments</comments>
		<pubDate>Thu, 29 Apr 2010 09:31:27 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR1]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[9iR2]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1020</guid>
		<description><![CDATA[Almost one year ago Iggy Fernandez asked me to write a short text for the Ask the Oracles column of the NoCOUG Journal. The topic was “Bind Variable Peeking: Bane or Boon?”. My text along with the ones of Wolfgang Breitling, Dan Tow and Jonathan Lewis were published in the August issue. For some (unknown) [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/04/bind-variable-peeking-bane-or-boon/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Exadata Storage Server and the Query Optimizer &#8211; Part 1</title>
		<link>http://antognini.ch/2010/04/exadata-storage-server-and-the-query-optimizer-part-1/</link>
		<comments>http://antognini.ch/2010/04/exadata-storage-server-and-the-query-optimizer-part-1/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 13:38:56 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Exadata]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1009</guid>
		<description><![CDATA[Even though the utilization of an Exadata Storage Server should be transparent for the query optimizer, when you look at execution plans generated in an environment using it you might notice slight differences. The purpose of this series of post is to summarize the differences I was able to observe.
Disclaimer: I do not have access [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/04/exadata-storage-server-and-the-query-optimizer-part-1/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Analyzing a SQL Trace File with SQL Statements</title>
		<link>http://antognini.ch/2010/04/analyzing-a-sql-trace-file-with-sql-statements/</link>
		<comments>http://antognini.ch/2010/04/analyzing-a-sql-trace-file-with-sql-statements/#comments</comments>
		<pubDate>Tue, 27 Apr 2010 08:34:42 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[SQL Trace]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=995</guid>
		<description><![CDATA[As of Oracle Database 11g the DBMS_SQLTUNE package provides the SELECT_SQL_TRACE function. Its purpose is to load the content of a SQL trace file into a SQL tuning set. But, as it often happens, a feature can be (mis)used for another purpose. The aim of this post is to show how to take advantage of [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/04/analyzing-a-sql-trace-file-with-sql-statements/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Tracing VPD Predicates</title>
		<link>http://antognini.ch/2010/02/tracing-vpd-predicates/</link>
		<comments>http://antognini.ch/2010/02/tracing-vpd-predicates/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 11:30:16 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR1]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[9iR2]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=106</guid>
		<description><![CDATA[Even though a number of articles and blog posts have already been written on this topic (e.g. on Pete Finnigan’s site I found references dating back from 2003), from time to time I’m still asked “How to trace predicates generated by VPD?”. Hence, here’s yet another blog post about this topic…
Let’s setup the scene before [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/02/tracing-vpd-predicates/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Does the Query Optimizer Cost PX Distribution Methods?</title>
		<link>http://antognini.ch/2010/01/does-the-query-optimizer-cost-px-distribution-methods/</link>
		<comments>http://antognini.ch/2010/01/does-the-query-optimizer-cost-px-distribution-methods/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 11:55:15 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR1]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[9iR2]]></category>
		<category><![CDATA[Parallel Processing]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=45</guid>
		<description><![CDATA[The short answer to this question is &#8220;yes&#8221;, it does. Unfortunately, the distribution costs are not externalized through the execution plans and, as a result, this limitation (yes, it is really a limitation in the current implementation, not a bug) confuses everyone that carefully look at the information provided in an execution plan of a [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/01/does-the-query-optimizer-cost-px-distribution-methods/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>
