<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16525" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>It's really a good question. We should know _which exactly
combinations are used internally_. (OS, File System, NAS/SAN).</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>In reality therse particular combinations are most stable and
preffered ones - no matter what is _officially certified_.</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=lfreitas34@yahoo.com href="mailto:lfreitas34@yahoo.com">Luis
Freitas</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=PRABHAKAR.TAMMINA@ORACLE.COM
href="mailto:PRABHAKAR.TAMMINA@ORACLE.COM">PRABHAKAR.TAMMINA@ORACLE.COM</A> ;
<A title=ocfs2-users@oss.oracle.com
href="mailto:ocfs2-users@oss.oracle.com">ocfs2-users@oss.oracle.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, August 22, 2007 6:46
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Ocfs2-users] Urgent :: 11i
on OCFS2.. I mean APPL_TOP,COMMON_TOP etc..</DIV>
<DIV><BR></DIV>
<DIV>Prabhakar,</DIV>
<DIV> </DIV>
<DIV> This post is only my personal opinion. I do not
work for Oracle nor have any close contact with the support and development
groups. But I never heard of anyone using this combination.</DIV>
<DIV> </DIV>
<DIV> This is kind of a gray area, since Oracle
usually provides support for OCFS2 in conjunction with RAC database. The APPS
people is a different group internally at Oracle, so even if this is
officially supported you could get into situations where the support analysts
start to redirect the TAR between these groups, or could argue that since the
issues are not related to Oracle Database or Oracle database binaries they
would not fix it.</DIV>
<DIV> </DIV>
<DIV> I would not do it unless with a very large
customer that could escalate any issues to get a fast resolution with
support. It probably is better to get a NAS storage and map it using
NFS.</DIV>
<DIV> </DIV>
<DIV> That said since it is supported for the database binaries,
there should not be immediate problems with other files. The FAQ about shared
APPL_TOP on metalink says that any disk sharing technology can be used.</DIV>
<DIV> </DIV>
<DIV> One thing that comes to my attention is that Oracle
Forms uses memory mapped files extensively. I dont know how completelly this
is implemented on OCFS2 and if it works well. Anyone can comment on
this? There are some posts on this list about problems with shared mmap.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Luis</DIV>
<DIV><BR><BR><B><I>PRABHAKAR.TAMMINA@ORACLE.COM</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">All,<BR><BR>Is
Shared APPL_TOP certified with 11i on OCFS2? Please send me the information
as soon as possible..<BR><BR>We have two RAC nodes on ASM file system and
one middle tier right now. Now want to setup Shared APPL_TOP so need your
help whether this is a certied with OCFS2 or not.<BR><BR>OS is SUSE 9
SP3.<BR><BR>Regards,<BR>Prabhakar
Tammina.<BR>(614)598-3487(cell).<BR><BR><BR>_______________________________________________<BR>Ocfs2-users
mailing
list<BR>Ocfs2-users@oss.oracle.com<BR>http://oss.oracle.com/mailman/listinfo/ocfs2-users<BR></BLOCKQUOTE><BR>
<P>
<HR SIZE=1>
Got a little couch potato? <BR>Check out fun <A
href="http://us.rd.yahoo.com/evt=48248/*http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz">summer
activities for kids.</A>
<P>
<HR>
<P></P>_______________________________________________<BR>Ocfs2-users mailing
list<BR>Ocfs2-users@oss.oracle.com<BR>http://oss.oracle.com/mailman/listinfo/ocfs2-users</BLOCKQUOTE></BODY></HTML>