Don't understand why would he want to set it to none.  I don't see any benefit of doing that.
By setting it to none, he disables Async IO and Direct IO.  A metalink discussion says
you would do it to avoid IO related OS bugs.  Were there any IO related problems with that
system?
 
Maybe someone with more insight to this can explain how this parameter is used in what
kind of situation.
 
Regards,
 
Richard
-----Original Message-----
From: John Shaw [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 2:44 PM
To: Multiple recipients of list ORACLE-L
Subject: filesystemio_options question

9.2.0.2, solaris 9 , Hitachi san
Before I got here the company had a consultant come in and configure the data warehouse instance. One of the init parameters he set was filesystemio_options=none. The jr. dba that is here recalled the reason he set it to none because it was using the san - is this really a good thing to do?

Reply via email to