Thanks, the problem is that now I'm working on a system with direct IO activated on the log_archive_dest filesystem (the SA told me that this was the workaroud for previous "performance problems")
OS: Solaris 8 Oracle: 8.1.7.4 OFA(including log_arch_dest): vxfs fstype mount output: /smsp_ofa on /dev/vx/dsk/osmspdg/smsp_ofa read/write/setuid/mincache=direct /convosync=direct/delaylog/largefiles/ioerror=mwdisable/dev=449022b
... and it's now that the arch processes are really not able to keep up with the log file switches: "cannot allocate new log" messages + shutdown abort from the SUN Cluster fault monitor for timeout ...
So I was wondering, could the direct IO be beneficial for the log_archive_dest filesystem in some cases?
Cheers Dimitre
-- -- Original Message -- -- From: John Smiley To: cichomitiko@(protected) Cc: oracle-l@(protected) Sent: Thursday, June 23, 2005 5:36 PM Subject: Re: Q: Filesystem choice for log_archive_dest
As long as your archiver processes are able to keep up with the log file switches, it doesn't matter what type of filesystem they're on. If you start seeing the archiver lag behind, or worse, you system comes to a screeching halt because it can't perform a log switch, you can increase the number of archive log processes (if the disks supporting the log archive dest(s) can handle more load) or store the archive logs on faster I/O. Typically this takes the form of LUNs on a RAID 1+0 using your file system of choice. For best performance, give the archivelogs their own set of disks.
John Smiley Technical Management Consultant TUSC, Inc.
On 6/23/05, Radoulov, Dimitre <cichomitiko@(protected)> wrote: Hi, could anyone provide guidelines for the log archive destination filesystem 's/IO type choice (both MS and *nix solutions would be interesting)?
Thanks, Dimitre
<!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.2900.2668" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>Thanks,</FONT></DIV> <DIV><FONT face=Arial size=2>the problem is that now I'm working on a system with direct IO activated on the log_archive_dest filesystem (the SA told me that this was the workaroud for previous "performance problems")</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>OS: Solaris 8</FONT></DIV> <DIV><FONT face=Arial size=2>Oracle: 8.1.7.4</FONT></DIV> <DIV><FONT face=Arial size=2>OFA(including log_arch_dest): vxfs fstype </FONT></DIV> <DIV><FONT face=Arial size=2>mount output:</FONT></DIV> <DIV><FONT face=Arial size=2>/smsp_ofa on /dev/vx/dsk/osmspdg/smsp_ofa read/write/setuid/mincache=direct/convosync=direct/delaylog/largefiles/ioerror =mwdisable/dev=449022b </FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>... and it's now that the arch processes are really not able to keep up with the log file switches: "cannot allocate new log" messages + shutdown abort from the SUN Cluster fault monitor for timeout ...</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>So I was wondering, could the direct IO be beneficial for the log_archive_dest filesystem in some cases? </FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>Cheers</FONT><BR>Dimitre </DIV> <DIV> </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=jrsmiley@(protected) href="mailto:jrsmiley@(protected)">John Smiley</A> </DIV> <DIV style="FONT: 10pt arial"><B>To:</B> <A title=cichomitiko@(protected) href="mailto:cichomitiko@(protected)">cichomitiko@(protected)</A> </DIV> <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=oracle-l@(protected) href="mailto:oracle-l@(protected)">oracle-l@(protected)</A> </DIV> <DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, June 23, 2005 5:36 PM</DIV> <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: Q: Filesystem choice for log_archive_dest</DIV> <DIV><BR></DIV> <DIV>As long as your archiver processes are able to keep up with the log file switches, it doesn't matter what type of filesystem they're on. If you start seeing the archiver lag behind, or worse, you system comes to a screeching halt because it can't perform a log switch, you can increase the number of archive log processes (if the disks supporting the log archive dest(s) can handle more load) or store the archive logs on faster I/O. Typically this takes the form of LUNs on a RAID 1+0 using your file system of choice. For best performance, give the archivelogs their own set of disks. </DIV> <DIV> </DIV> <DIV>John Smiley</DIV> <DIV>Technical Management Consultant</DIV> <DIV>TUSC, Inc.<BR><BR> </DIV> <DIV><SPAN class=gmail_quote>On 6/23/05, <B class=gmail_sendername>Radoulov, Dimitre</B> <<A href="mailto:cichomitiko@(protected)">cichomitiko@(protected)</A>> wrote:</SPAN> <BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <DIV><FONT face=Arial size=2>Hi,</FONT></DIV> <DIV><FONT face=Arial size=2>could anyone provide guidelines for the log archive destination filesystem's/IO type choice (both MS and *nix solutions would be interesting)?</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV>Thanks,<BR>Dimitre </DIV> <DIV> </DIV> <DIV> </DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>
