Yeah, the Netapp documents are not consistent. <br>This is what we have for our oracle mounts:<br>nfs 2 yes rw,bg,vers=3,proto=tcp,hard,intr,rsize=32768,wsize=32768,forcedirectio,llock&nbsp; &lt;&lt;--- For all data files, redo logs and arch log volumes.
<br>and no forceddirectio for the Oracle binaries volume<br>nfs 2 yes rw,bg,vers=3,proto=tcp,hard,intr,rsize=32768,wsize=32768,llock<br><br>Is this correct? It seems to be working OK for us now, we are yet to go into production though, its only a few developers working on the database.
<br>BTW, we are on Solaris 10.<br>-G<br><br><div><span class="gmail_quote">On 5/2/07, <b class="gmail_sendername">Carl Howell</b> &lt;<a href="mailto:chowell@uwf.edu">chowell@uwf.edu</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In TR-3322 it says that the mount point for the redo logs should have the<br>forcedirectio option on and the mount point for the data files should have<br>it off. KB7518, which appears to be more recent, doesn&#39;t say anything about
<br>mount options for redo log volumes, but I assume you should have either<br>forcedirectio or llock on both the mount points for your redo logs and data<br>files. Is this correct?<br><br>Thanks,<br><br>- Carl<br><br></blockquote>
</div><br>