<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Oracle diagnostic events Part 5</title>
	<atom:link href="http://oraclue.com/2009/06/02/oracle-diagnostic-events-part-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://oraclue.com/2009/06/02/oracle-diagnostic-events-part-5/</link>
	<description>Oracle internals, debugging and undocumented features</description>
	<lastBuildDate>Thu, 27 Oct 2011 15:05:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: oraclue</title>
		<link>http://oraclue.com/2009/06/02/oracle-diagnostic-events-part-5/#comment-214</link>
		<dc:creator><![CDATA[oraclue]]></dc:creator>
		<pubDate>Thu, 18 Jun 2009 17:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://oraclue.wordpress.com/?p=678#comment-214</guid>
		<description><![CDATA[For example this command:

alter session set events &#039;trace[sql_mon.*] memory=high&#039;;

will trace in-memory SQL_MONITOR component ( target ) and all sub component at level high.
There are different targets that you can use.I already posted some of them.Others I intentionally left out ( dangers etc ).


I did not have a chance to play much with all of these events options because there is so many of them.
It took me long time just to post a correct syntax.That&#039;s how big event syntax is.And I am not finished yet.More to come.

Best way would be to run these command with different levels and see the difference.
I will do it when I get some free time.

Thanks,

Miladin]]></description>
		<content:encoded><![CDATA[<p>For example this command:</p>
<p>alter session set events &#8216;trace[sql_mon.*] memory=high&#8217;;</p>
<p>will trace in-memory SQL_MONITOR component ( target ) and all sub component at level high.<br />
There are different targets that you can use.I already posted some of them.Others I intentionally left out ( dangers etc ).</p>
<p>I did not have a chance to play much with all of these events options because there is so many of them.<br />
It took me long time just to post a correct syntax.That&#8217;s how big event syntax is.And I am not finished yet.More to come.</p>
<p>Best way would be to run these command with different levels and see the difference.<br />
I will do it when I get some free time.</p>
<p>Thanks,</p>
<p>Miladin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mladen Gogala</title>
		<link>http://oraclue.com/2009/06/02/oracle-diagnostic-events-part-5/#comment-211</link>
		<dc:creator><![CDATA[Mladen Gogala]]></dc:creator>
		<pubDate>Thu, 18 Jun 2009 11:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://oraclue.wordpress.com/?p=678#comment-211</guid>
		<description><![CDATA[Miladin, I am unclear about the memory option. What does the memory=high option means and what additional information will be provided in the resulting trace file? Keep up the good work!]]></description>
		<content:encoded><![CDATA[<p>Miladin, I am unclear about the memory option. What does the memory=high option means and what additional information will be provided in the resulting trace file? Keep up the good work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

