<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>direct path read &#8211; Bugra Parlayan | Oracle Database &amp; Exadata Blog</title>
	<atom:link href="https://www.bugraparlayan.com.tr/tag/direct-path-read/feed" rel="self" type="application/rss+xml" />
	<link>https://www.bugraparlayan.com.tr</link>
	<description>A technical blog</description>
	<lastBuildDate>Sat, 19 Jul 2025 19:07:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>

<image>
	<url>https://www.bugraparlayan.com.tr/wp-content/uploads/2020/06/cropped-plsql-32x32.jpg</url>
	<title>direct path read &#8211; Bugra Parlayan | Oracle Database &amp; Exadata Blog</title>
	<link>https://www.bugraparlayan.com.tr</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Creating an ASM Disk on Exadata FlashDisk</title>
		<link>https://www.bugraparlayan.com.tr/creating-an-asm-disk-on-exadata-flashdisk.html</link>
		
		<dc:creator><![CDATA[Bugra Parlayan]]></dc:creator>
		<pubDate>Sat, 19 Jul 2025 19:06:23 +0000</pubDate>
				<category><![CDATA[Engineered Systems]]></category>
		<category><![CDATA[ASM]]></category>
		<category><![CDATA[direct path read]]></category>
		<category><![CDATA[disk drop]]></category>
		<category><![CDATA[exadata]]></category>
		<category><![CDATA[flash cache]]></category>
		<category><![CDATA[FlashDisk]]></category>
		<category><![CDATA[performance tuning]]></category>
		<category><![CDATA[planned maintenance]]></category>
		<category><![CDATA[Temp Tablespace]]></category>
		<category><![CDATA[warm-up effect]]></category>
		<guid isPermaLink="false">https://www.bugraparlayan.com.tr/?p=1505</guid>

					<description><![CDATA[<p>Recently, we noticed performance drops at certain times on an Exadata server operating as a data warehouse (DWH). Upon analyzing AWR reports, the following wait event stood out: direct path read/write temp waits We knew this event was caused by temporary (temp) data being written to or read from disk during query execution. Although we &#8230;</p>
<p>The post <a rel="nofollow" href="https://www.bugraparlayan.com.tr/creating-an-asm-disk-on-exadata-flashdisk.html">Creating an ASM Disk on Exadata FlashDisk</a> appeared first on <a rel="nofollow" href="https://www.bugraparlayan.com.tr">Bugra Parlayan | Oracle Database &amp; Exadata Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Recently, we noticed performance drops at certain times on an Exadata server operating as a data warehouse (DWH). Upon analyzing <strong>AWR reports</strong>, the following wait event stood out:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>direct path read/write temp waits</p>
</blockquote>



<p>We knew this event was caused by temporary (temp) data being written to or read from disk during query execution. Although we had applied various SQL optimizations, they did not significantly reduce the wait times.</p>



<h3 class="wp-block-heading"><strong>Root Cause: Heavy TEMP Tablespace Usage</strong></h3>



<p>Large SQL queries in data warehouses—especially those involving operations like hash joins, sorts, and group by—require extensive use of TEMP space. In our case, the <strong>TEMP tablespace</strong> was located on <em>high-latency</em> disk groups by default, which increased IO wait times.</p>



<h3 class="wp-block-heading"><strong>Solution: Move TEMP Tablespace to FlashDisk on Exadata</strong></h3>



<p>To directly improve performance, we decided to move the TEMP tablespace to the <strong>FlashDisk</strong> layer on Exadata. This layer offers much higher IO throughput compared to traditional disks, making it particularly advantageous for handling temporary data operations.</p>



<p><br>P.S. Since we will drop and recreate the existing flash disks during this operation, there may be minor negative impacts during the process and until the flash cache warms up again. Therefore, this work should be performed during a planned and quiet maintenance window.</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
dcli –g cell_group –l root cellcli -e &quot;alter flashcache all flush&quot;
dcli -g cell_group -l root cellcli -e &quot;LIST CELLDISK ATTRIBUTES name, flushstatus, flusherror&quot; | grep FD
dcli -g cell_group -l root cellcli -e drop flashcache
dcli -g cell_group -l root cellcli -e create flashcache all size=20.2875976562500T;
dcli -g cell_group -l root cellcli -e CREATE GRIDDISK ALL FLASHDISK PREFIX='FLASHTMP';

</pre></div>

<div class="wp-block-syntaxhighlighter-code "><pre class="brush: sql; title: ; notranslate">
sqlplus / as sysasm

alter system set asm_diskstring='o/*/DATA_*','o/*/RECO_*','o/*/FLASHTMP*';

CREATE diskgroup TEMPDG normal redundancy disk 'o/*/FLASHTMP*' attribute 'compatible.rdbms'='19.0.0.0.0', 'compatible.asm'='19.0.0.0.0', 'cell.smart_scan_capable'='TRUE', 'au_size'='4M';
</pre></div>

<div class="wp-block-syntaxhighlighter-code "><pre class="brush: sql; title: ; notranslate">
sqlplus &amp; as sysdba

CREATE TEMPORARY TABLESPACE TEMP_FLASH TEMPFILE '+ TEMPDG' SIZE 32G EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP_FLASH;

DROP TABLESPACE TEMP INCLUDING CONTENTS AND DATAFILES;

</pre></div><p>The post <a rel="nofollow" href="https://www.bugraparlayan.com.tr/creating-an-asm-disk-on-exadata-flashdisk.html">Creating an ASM Disk on Exadata FlashDisk</a> appeared first on <a rel="nofollow" href="https://www.bugraparlayan.com.tr">Bugra Parlayan | Oracle Database &amp; Exadata Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
