<?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>Oracle - Concepts et Exemples &#187; db file sequential read</title>
	<atom:link href="https://blog.developpez.com/pachot/tag/db-file-sequential-read/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.developpez.com/pachot</link>
	<description>Les fonctionalités et concepts d&#039;Oracle à partir de traductions et de démos</description>
	<lastBuildDate>Sun, 03 Apr 2016 20:36:21 +0000</lastBuildDate>
	<language>fr-FR</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>12c: des noms de Wait Events plus parlants</title>
		<link>https://blog.developpez.com/pachot/12c_display_name/</link>
		<comments>https://blog.developpez.com/pachot/12c_display_name/#comments</comments>
		<pubDate>Mon, 28 Oct 2013 17:05:34 +0000</pubDate>
		<dc:creator><![CDATA[pachot]]></dc:creator>
				<category><![CDATA[12c]]></category>
		<category><![CDATA[db file sequential read]]></category>
		<category><![CDATA[db file squattered read]]></category>
		<category><![CDATA[wait events]]></category>

		<guid isPermaLink="false">http://blog.developpez.com/pachot/?p=871</guid>
		<description><![CDATA[Certains noms de wait events sont trompeurs. C&#8217;est le cas par exemple de &#8216;db file sequential read&#8217; qui n&#8217;est pas ce qu&#8217;on entend par lecture disque séquentielle, mais plutôt une lecture monobloc (donc plutôt des i/o randoms). Alors que &#8216;log &#8230; <a href="https://blog.developpez.com/pachot/12c_display_name/">Lire la suite <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Certains noms de wait events sont trompeurs. C&rsquo;est le cas par exemple de &lsquo;db file sequential read&rsquo; qui n&rsquo;est pas ce qu&rsquo;on entend par lecture disque séquentielle, mais plutôt une lecture monobloc (donc plutôt des i/o randoms).<br />
Alors que &lsquo;log file sequential read&rsquo; est bien une lecture de plusieurs blocs contigus.</p>
<p>La <a href="http://docs.oracle.com/cd/E16655_01/server.121/e17615/waitevents003.htm#BGGIBDJI" title="doc">doc</a> précise leur définition, mais en 12c on a aussi un &lsquo;Display Name&rsquo; qui permet à Oracle de montrer un nom un peu plus parlant.</p>
<p>Voici ceux dont le &lsquo;display name&rsquo; est différent du nom de l&rsquo;event:</p>
<pre>select wait_class,name, display_name from v$event_name where display_name != name order by 1,2;</pre>
<table>
<tr>
<th scope="col">WAIT_CLASS
</th>
<th scope="col">NAME
</th>
<th scope="col">DISPLAY_NAME
</th>
</tr>
<tr>
<td>Administrative
</td>
<td>concurrent I/O completion
</td>
<td>online move datafile IO completion
</td>
</tr>
<tr>
<td>Administrative
</td>
<td>datafile copy range completion
</td>
<td>online move datafile copy range completion
</td>
</tr>
<tr>
<td>Administrative
</td>
<td>wait for possible quiesce finish
</td>
<td>quiesce database completion
</td>
</tr>
<tr>
<td>Commit
</td>
<td>log file sync
</td>
<td>commit: log file sync
</td>
</tr>
<tr>
<td>Configuration
</td>
<td>log buffer space
</td>
<td>log buffer full &#8211; LGWR bottleneck
</td>
</tr>
<tr>
<td>Idle
</td>
<td>LGWR real time apply sync
</td>
<td>standby apply advance notification
</td>
</tr>
<tr>
<td>Other
</td>
<td>DFS db file lock
</td>
<td>quiesce for datafile offline
</td>
</tr>
<tr>
<td>Other
</td>
<td>Image redo gen delay
</td>
<td>redo resource management
</td>
</tr>
<tr>
<td>Other
</td>
<td>datafile move cleanup during resize
</td>
<td>online move datafile resize cleanup
</td>
</tr>
<tr>
<td>System I/O
</td>
<td>control file sequential read
</td>
<td>control file read
</td>
</tr>
<tr>
<td>System I/O
</td>
<td>control file single write
</td>
<td>control file write
</td>
</tr>
<tr>
<td>System I/O
</td>
<td>db file parallel write
</td>
<td>db list of blocks write
</td>
</tr>
<tr>
<td>System I/O
</td>
<td>log file parallel write
</td>
<td>log file redo write
</td>
</tr>
<tr>
<td>System I/O
</td>
<td><strong>log file sequential read</strong>
</td>
<td><strong>log file multiblock read</strong>
</td>
</tr>
<tr>
<td>System I/O
</td>
<td>log file single write
</td>
<td>log file header write
</td>
</tr>
<tr>
<td>User I/O
</td>
<td>db file parallel read
</td>
<td>db list of blocks read
</td>
</tr>
<tr>
<td>User I/O
</td>
<td><strong>db file scattered read</strong>
</td>
<td><strong>db multiblock read</strong>
</td>
</tr>
<tr>
<td>User I/O
</td>
<td><strong>db file sequential read</strong>
</td>
<td><strong>db single block read</strong>
</td>
</tr>
<tr>
<td>User I/O
</td>
<td>db file single write
</td>
<td>db single block write
</td>
</tr>
</table>
<p>La différentiation des i/o single block et multiblock est particulièrement intéressante.</p>
]]></content:encoded>
			<wfw:commentRss></wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
