<?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: Autoallocate and PX</title>
	<atom:link href="http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/feed/" rel="self" type="application/rss+xml" />
	<link>http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/</link>
	<description>Just another Oracle weblog</description>
	<lastBuildDate>Fri, 24 May 2013 13:27:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: PX and system allocation &#171; Oracle Scratchpad</title>
		<link>http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-47157</link>
		<dc:creator><![CDATA[PX and system allocation &#171; Oracle Scratchpad]]></dc:creator>
		<pubDate>Thu, 14 Jun 2012 17:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-47157</guid>
		<description><![CDATA[[...] few years ago (2007) I wrote about a problem that could appear when you mixed parallel execution with system managed extent allocation. A couple of years later I added a note that Christian Antognini had observed a patch in 11.1.0.7 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] few years ago (2007) I wrote about a problem that could appear when you mixed parallel execution with system managed extent allocation. A couple of years later I added a note that Christian Antognini had observed a patch in 11.1.0.7 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amir Riaz</title>
		<link>http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-37612</link>
		<dc:creator><![CDATA[Amir Riaz]]></dc:creator>
		<pubDate>Sun, 24 Oct 2010 09:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-37612</guid>
		<description><![CDATA[Jonathon,

That &#039;s solve our problem. we have a huge data warehouse with 32K block size and with quite a good IO system with oracle 11r2. but we never manage to get db_file_multiblock_read_count=128 and we have alot of holes in tablespace also. Now we are setting initial=8M but not able to decide Next value.  Also a value of db_file_multiblock_read_count=256 is under discussion. our system admin says that we can change this value by setting the maxphy tunable parameter of solaris.]]></description>
		<content:encoded><![CDATA[<p>Jonathon,</p>
<p>That &#8216;s solve our problem. we have a huge data warehouse with 32K block size and with quite a good IO system with oracle 11r2. but we never manage to get db_file_multiblock_read_count=128 and we have alot of holes in tablespace also. Now we are setting initial=8M but not able to decide Next value.  Also a value of db_file_multiblock_read_count=256 is under discussion. our system admin says that we can change this value by setting the maxphy tunable parameter of solaris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 碎片(Fragmentation)&#8211;介绍 &#171; a db thinker&#039;s home</title>
		<link>http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-36865</link>
		<dc:creator><![CDATA[碎片(Fragmentation)&#8211;介绍 &#171; a db thinker&#039;s home]]></dc:creator>
		<pubDate>Tue, 27 Jul 2010 07:21:54 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-36865</guid>
		<description><![CDATA[[...] 假如说,每个区间都只能是64K,这会限制我们将发起的“db file multiblock read”请求的大小吗或者这些请求可以跨越区间边界读取吗?如果这个表空间是有两个(或多个)数据文件组成,而这些区间又是以“轮流”在两个文件之间分配的,这会影响读操作的方式吗?如果我们尝试进行并行表扫描,这些限制在“direct path read”上会不会有所不同呢?如果你的运行系统是一个数据仓库,需要花费大量的时间运行这种操作,那么这些就是你需要回答的问题.(例如,参见我3年前写的关于运行并行查询时的部分IO异常的记录,以及Christian Antognini在大约几年后描述的Oracle 11g中的一个相关改进.) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 假如说,每个区间都只能是64K,这会限制我们将发起的“db file multiblock read”请求的大小吗或者这些请求可以跨越区间边界读取吗?如果这个表空间是有两个(或多个)数据文件组成,而这些区间又是以“轮流”在两个文件之间分配的,这会影响读操作的方式吗?如果我们尝试进行并行表扫描,这些限制在“direct path read”上会不会有所不同呢?如果你的运行系统是一个数据仓库,需要花费大量的时间运行这种操作,那么这些就是你需要回答的问题.(例如,参见我3年前写的关于运行并行查询时的部分IO异常的记录,以及Christian Antognini在大约几年后描述的Oracle 11g中的一个相关改进.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fragmentation 1 &#171; Oracle Scratchpad</title>
		<link>http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-36739</link>
		<dc:creator><![CDATA[Fragmentation 1 &#171; Oracle Scratchpad]]></dc:creator>
		<pubDate>Tue, 13 Jul 2010 20:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-36739</guid>
		<description><![CDATA[[...] type of operation then these are just some of the questions you need to answer. (See, for example, a note I wrote three years ago about some of the anomalies of I/O sizes when running parallel query, and a related enhancement in [...]]]></description>
		<content:encoded><![CDATA[<p>[...] type of operation then these are just some of the questions you need to answer. (See, for example, a note I wrote three years ago about some of the anomalies of I/O sizes when running parallel query, and a related enhancement in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted</title>
		<link>http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-10229</link>
		<dc:creator><![CDATA[Ted]]></dc:creator>
		<pubDate>Wed, 30 May 2007 18:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/2007/05/29/autoallocate-and-px/#comment-10229</guid>
		<description><![CDATA[Fantastic,
This clearly explains some of the issues I&#039;ve been seeing and have been experimenting over the last week.
Works done now.... Thanks Jonathan.]]></description>
		<content:encoded><![CDATA[<p>Fantastic,<br />
This clearly explains some of the issues I&#8217;ve been seeing and have been experimenting over the last week.<br />
Works done now&#8230;. Thanks Jonathan.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
