<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: New Information in SQL Trace Files</title>
	<atom:link href="http://antognini.ch/2008/09/new-information-in-sql-trace-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://antognini.ch/2008/09/new-information-in-sql-trace-files/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Sep 2010 09:31:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mathew Butler</title>
		<link>http://antognini.ch/2008/09/new-information-in-sql-trace-files/comment-page-1/#comment-90</link>
		<dc:creator>Mathew Butler</dc:creator>
		<pubDate>Mon, 22 Sep 2008 09:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://antognini.ch/?p=48#comment-90</guid>
		<description>Hi Chris,

Interesting. This then adds value to tracing at level 4 (provided the cursor is still cached ),
since tracing at levels higher than 4 will already include the execution plan in the trace file.

I think I will still prefer to use level 8, or 12 when tracing. I like that all the information for analysis is tyhen captured in the one file.

Regards,

M.</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>Interesting. This then adds value to tracing at level 4 (provided the cursor is still cached ),<br />
since tracing at levels higher than 4 will already include the execution plan in the trace file.</p>
<p>I think I will still prefer to use level 8, or 12 when tracing. I like that all the information for analysis is tyhen captured in the one file.</p>
<p>Regards,</p>
<p>M.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Antognini</title>
		<link>http://antognini.ch/2008/09/new-information-in-sql-trace-files/comment-page-1/#comment-89</link>
		<dc:creator>Christian Antognini</dc:creator>
		<pubDate>Sun, 21 Sep 2008 20:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://antognini.ch/?p=48#comment-89</guid>
		<description>Hi Mathew

You are right. There is this enhancement as well. The field &quot;plh&quot; is the hash value of the execution plan. In other words, it matches the column plan_hash_value in v$sql_plan (and similar views...). This is an interesting information when a given SQL statement has several child cursors.

Best regards,
Chris</description>
		<content:encoded><![CDATA[<p>Hi Mathew</p>
<p>You are right. There is this enhancement as well. The field &#8220;plh&#8221; is the hash value of the execution plan. In other words, it matches the column plan_hash_value in v$sql_plan (and similar views&#8230;). This is an interesting information when a given SQL statement has several child cursors.</p>
<p>Best regards,<br />
Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mathew Butler</title>
		<link>http://antognini.ch/2008/09/new-information-in-sql-trace-files/comment-page-1/#comment-88</link>
		<dc:creator>Mathew Butler</dc:creator>
		<pubDate>Sun, 21 Sep 2008 20:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://antognini.ch/?p=48#comment-88</guid>
		<description>I see that lines associated with a cursor also have a new component &quot;plh=&quot;

I wonder if this is a handle to reference the source of the SQL? ie: Ease the identification of SQL sourced in the same stored procedure/package?

M</description>
		<content:encoded><![CDATA[<p>I see that lines associated with a cursor also have a new component &#8220;plh=&#8221;</p>
<p>I wonder if this is a handle to reference the source of the SQL? ie: Ease the identification of SQL sourced in the same stored procedure/package?</p>
<p>M</p>
]]></content:encoded>
	</item>
</channel>
</rss>
