<?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: How to Read PGA Memory Advisory Section in AWR and Statspack Reports</title>
	<atom:link href="http://www.onlyring.net/2009/08/29/oracle-rdbms/how-to-read-pga-memory-advisory-section-in-awr-and-statspack-reports.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.onlyring.net/2009/08/29/oracle-rdbms/how-to-read-pga-memory-advisory-section-in-awr-and-statspack-reports.html</link>
	<description>记录工作，记录生活，记录一切值得留下的东西...</description>
	<lastBuildDate>Tue, 22 Nov 2011 06:19:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: jmavr</title>
		<link>http://www.onlyring.net/2009/08/29/oracle-rdbms/how-to-read-pga-memory-advisory-section-in-awr-and-statspack-reports.html/comment-page-1#comment-7928</link>
		<dc:creator>jmavr</dc:creator>
		<pubDate>Fri, 16 Jul 2010 06:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.onlyring.net/?p=104#comment-7928</guid>
		<description>Beginning with Oracle Database 11g, Oracle Database can manage the SGA memory and instance PGA memory completely automatically. You designate only the total memory size to be used by the instance, and Oracle Database dynamically exchanges memory between the SGA and the instance PGA as needed to meet processing demands. This capability is referred to as automatic memory management. With this memory management method, the database also dynamically tunes the sizes of the individual SGA components and the sizes of the individual PGAs.

To achieve this, two new parameters have been introduced named MEMORY_MAX_TARGET and MEMORY_TARGET. To do so (on most platforms), you set only a target memory size initialization parameter (MEMORY_TARGET) and optionally a maximum memory size initialization parameter (MEMORY_MAX_TARGET).</description>
		<content:encoded><![CDATA[<p>Beginning with Oracle Database 11g, Oracle Database can manage the SGA memory and instance PGA memory completely automatically. You designate only the total memory size to be used by the instance, and Oracle Database dynamically exchanges memory between the SGA and the instance PGA as needed to meet processing demands. This capability is referred to as automatic memory management. With this memory management method, the database also dynamically tunes the sizes of the individual SGA components and the sizes of the individual PGAs.</p>
<p>To achieve this, two new parameters have been introduced named MEMORY_MAX_TARGET and MEMORY_TARGET. To do so (on most platforms), you set only a target memory size initialization parameter (MEMORY_TARGET) and optionally a maximum memory size initialization parameter (MEMORY_MAX_TARGET).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kostas Hairopoulos</title>
		<link>http://www.onlyring.net/2009/08/29/oracle-rdbms/how-to-read-pga-memory-advisory-section-in-awr-and-statspack-reports.html/comment-page-1#comment-6370</link>
		<dc:creator>Kostas Hairopoulos</dc:creator>
		<pubDate>Mon, 19 Apr 2010 19:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.onlyring.net/?p=104#comment-6370</guid>
		<description>I am wondering the reason the specific Metalin document (786554.1) is applicable up to 10.2.0.4 and not 11g</description>
		<content:encoded><![CDATA[<p>I am wondering the reason the specific Metalin document (786554.1) is applicable up to 10.2.0.4 and not 11g</p>
]]></content:encoded>
	</item>
</channel>
</rss>

