<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blog.trivadis.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Striving for Optimal Performance (Christian Antognini)</title><link>http://blog.trivadis.com/blogs/christianantognini/default.aspx</link><description>This blog is a mirror of http://antognini.ch/blog</description><dc:language /><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>PerformaSure X-Agent Configuration</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2009/01/05/performasure-x-agent-configuration.aspx</link><pubDate>Mon, 05 Jan 2009 17:47:42 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:18399</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=18399</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2009/01/05/performasure-x-agent-configuration.aspx#comments</comments><description>PerformaSure of Quest Software is a J2EE performance diagnosis tool that provides an end-to-end transaction-centric view of performance as experienced by end users. To gather profile information PerformaSure uses one or several agents deployed on the...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2009/01/05/performasure-x-agent-configuration.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=18399" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/PerformaSure/default.aspx">PerformaSure</category></item><item><title>What Are Hints?</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/22/what-are-hints.aspx</link><pubDate>Mon, 22 Dec 2008 07:43:32 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:15590</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=15590</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/22/what-are-hints.aspx#comments</comments><description>Yesterday, while reading a swiss italian dialect tranlation of Le petit prince (entitled Ul principe pinin), I noticed a very interesting discussion between the little prince and the king (the inhabitant of the first planet visited by the little prince&amp;#8230;...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/22/what-are-hints.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=15590" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TOP/default.aspx">TOP</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Query+Optimizer/default.aspx">Query Optimizer</category></item><item><title>Automatic Evolution of SQL Plan Baselines</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/10/automatic-evolution-of-sql-plan-baselines.aspx</link><pubDate>Wed, 10 Dec 2008 16:00:53 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:12884</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=12884</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/10/automatic-evolution-of-sql-plan-baselines.aspx#comments</comments><description>In the section Evolving SQL Plan Baselines of TOP (pages 299-300) I explain what an evolution is and how to manually do it. What I do not cover is the automatic evolution. In fact, I wrote only the following text about it: &amp;#8220;In addition to the manual...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/10/automatic-evolution-of-sql-plan-baselines.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=12884" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TOP/default.aspx">TOP</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Query+Optimizer/default.aspx">Query Optimizer</category></item><item><title>Query Optimizer 11g – What’s new?</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/02/query-optimizer-11g-what-s-new.aspx</link><pubDate>Tue, 02 Dec 2008 21:01:09 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:11188</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=11188</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/02/query-optimizer-11g-what-s-new.aspx#comments</comments><description>Today I presented at the DOAG Conference in Nuremberg. As the title of this post suggests, I talked about the query optimizer features introduced in Oracle Database 11g. This is an evolution of the paper I already presented at the UKOUG Conference in...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/12/02/query-optimizer-11g-what-s-new.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=11188" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Query+Optimizer/default.aspx">Query Optimizer</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Speaking/default.aspx">Speaking</category></item><item><title>DBMS_XPLAN.PREPARE_PLAN_XML_QUERY</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/21/dbms-xplan-prepare-plan-xml-query.aspx</link><pubDate>Fri, 21 Nov 2008 11:11:39 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:7108</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=7108</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/21/dbms-xplan-prepare-plan-xml-query.aspx#comments</comments><description>As of 11.1.0.7 in the package dbms_xplan there is a new function:
FUNCTION prepare_plan_xml_query(plan_query IN VARCHAR2) RETURN VARCHAR2;
Simply put, the function takes as input a query that extract information from a plan table (e.g. plan_table or v...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/21/dbms-xplan-prepare-plan-xml-query.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=7108" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Query+Optimizer/default.aspx">Query Optimizer</category></item><item><title>TVD$XTAT 4.0 Beta 8</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/17/tvd-xtat-4-0-beta-8.aspx</link><pubDate>Mon, 17 Nov 2008 20:08:13 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:6024</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=6024</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/17/tvd-xtat-4-0-beta-8.aspx#comments</comments><description>This is just a short note to point out that I just uploaded under the section Downloadable Files of TOP a new version of TVD$XTAT.
The change log since Beta 7 is the following: Improved generation of synthetic cursors (particularly for RPC and XCTEND...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/17/tvd-xtat-4-0-beta-8.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=6024" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TOP/default.aspx">TOP</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/SQL+Trace/default.aspx">SQL Trace</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TVD_2400_XTAT/default.aspx">TVD$XTAT</category></item><item><title>Hotsos Symposium 2009</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/13/hotsos-symposium-2009.aspx</link><pubDate>Thu, 13 Nov 2008 05:00:27 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:4777</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=4777</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/13/hotsos-symposium-2009.aspx#comments</comments><description>Every March since 2004 I use to spend several days in Dallas. The reason is quite simple… people from around the world sharing my own interests gather there to attend Hotsos Symposium. If, like me, you are focusing on getting the most out of Oracle, this...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/13/hotsos-symposium-2009.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=4777" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Speaking/default.aspx">Speaking</category></item><item><title>Invisible Indexes and Hints</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/11/invisible-indexes-and-hints.aspx</link><pubDate>Tue, 11 Nov 2008 16:02:32 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:4698</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=4698</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/11/invisible-indexes-and-hints.aspx#comments</comments><description>In this post I would like to remove some misinformation about the utilization of hints with invisible indexes.
Let’s start by providing you what two sources say about that topic: Oracle Database 11g: New Features for DBAs and Developers (by Sam R. Alapati...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/11/11/invisible-indexes-and-hints.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=4698" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Query+Optimizer/default.aspx">Query Optimizer</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Indexes/default.aspx">Indexes</category></item><item><title>Introduce TVD$XTAT</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/24/introduce-tvd-xtat.aspx</link><pubDate>Fri, 24 Oct 2008 13:56:51 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:2659</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=2659</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/24/introduce-tvd-xtat.aspx#comments</comments><description>Trivadis Extended Tracefile Analysis Tool (TVD$XTAT) is a command-line tool. Like TKPROF, its main purpose is to take a raw SQL trace file as input and generate a formatted file as output.
Why Is TKPROF Not Enough?
In late 1999, I had my first encounter...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/24/introduce-tvd-xtat.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=2659" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TOP/default.aspx">TOP</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/SQL+Trace/default.aspx">SQL Trace</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TVD_2400_XTAT/default.aspx">TVD$XTAT</category></item><item><title>Invisible Indexes and Locks</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/17/invisible-indexes-and-locks.aspx</link><pubDate>Fri, 17 Oct 2008 08:33:23 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:2361</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=2361</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/17/invisible-indexes-and-locks.aspx#comments</comments><description>Invisible indexes are useful to temporarily hide an index from the query optimizer. In this post, instead of explaining what invisible indexes are, I would like to show whether the database engine uses invisible indexes to avoid false contention caused...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/17/invisible-indexes-and-locks.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=2361" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Indexes/default.aspx">Indexes</category></item><item><title>TOP on Google Book Search</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/10/top-on-google-book-search.aspx</link><pubDate>Fri, 10 Oct 2008 09:43:42 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:1949</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=1949</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/10/top-on-google-book-search.aspx#comments</comments><description>This is a short note to point out that my book, Troubleshooting Oracle Performance, is available on Google Book Search. To browse through it or to use the search capabilities provided by Google, click here. Even if the preview is limited to certain number...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/10/top-on-google-book-search.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=1949" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TOP/default.aspx">TOP</category></item><item><title>Granularity ‘APPROX_GLOBAL AND PARTITION’</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/03/granularity-approx-global-and-partition.aspx</link><pubDate>Fri, 03 Oct 2008 08:27:19 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:1781</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=1781</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/03/granularity-approx-global-and-partition.aspx#comments</comments><description>The patchset 11.1.0.7 introduces in the package DBMS_STATS a new value for the parameter GRANULARITY. The description provided by the development team in $ORACLE_HOME/rdbms/admin/dbmsstat.sql is the following:
&amp;#039;APPROX_GLOBAL AND PARTITION&amp;#039; ...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/10/03/granularity-approx-global-and-partition.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=1781" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Object+Statistics/default.aspx">Object Statistics</category></item><item><title>Bloom Filters</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/26/bloom-filters.aspx</link><pubDate>Fri, 26 Sep 2008 16:24:13 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:1669</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=1669</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/26/bloom-filters.aspx#comments</comments><description>Oracle Database, as of 10g Release 2, uses bloom filters in various situations. Unfortunately, no information about their usage is available in Oracle documentation. For this reason, I decided to write a paper to explain not only what bloom filters are...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/26/bloom-filters.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=1669" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/10gR2/default.aspx">10gR2</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Query+Optimizer/default.aspx">Query Optimizer</category></item><item><title>Book Presentation</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/23/book-presentation.aspx</link><pubDate>Tue, 23 Sep 2008 21:40:34 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:1617</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=1617</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/23/book-presentation.aspx#comments</comments><description>I already pointed out in a previous post that Tanel Poder will be speaking in Vienna, Düsseldorf, Munich and Zürich next December. The news is that an additional presentation (followed by an aperitif) will take place at the same locations and dates as...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/23/book-presentation.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=1617" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/TOP/default.aspx">TOP</category><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/Speaking/default.aspx">Speaking</category></item><item><title>New Information in SQL Trace Files</title><link>http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/21/new-information-in-sql-trace-files.aspx</link><pubDate>Sun, 21 Sep 2008 19:34:47 GMT</pubDate><guid isPermaLink="false">7f420732-9615-472e-9723-d9bd9f35b01c:1563</guid><dc:creator>Striving for Optimal Performance</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blog.trivadis.com/blogs/christianantognini/rsscomments.aspx?PostID=1563</wfw:commentRss><comments>http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/21/new-information-in-sql-trace-files.aspx#comments</comments><description>During some tests with patchset 11.1.0.7 (which is presently available for Linux 32-bit and 64-bit only) I noticed something new in the SQL trace files. Let&amp;#8217;s see what is the difference if I run the following statements with and without the patchset...(&lt;a href="http://blog.trivadis.com/blogs/christianantognini/archive/2008/09/21/new-information-in-sql-trace-files.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blog.trivadis.com/aggbug.aspx?PostID=1563" width="1" height="1"&gt;</description><category domain="http://blog.trivadis.com/blogs/christianantognini/archive/tags/11gR1/default.aspx">11gR1</category></item></channel></rss>