Which filesystem/volume manager are you using, if any? That is potentially where you would want to look if the async write queue is getting backed up. Just shutting off async is a terrible suggestion from EMC. I am suprised at them.
-- Jeremiah Wilton http://www.speakeasy.net/~jwilton On Mon, 15 Apr 2002, Scott Canaan wrote: > We have implemented a Sun Solaris Cluster (4 machines), connected to > an EMC storage array. The migration began last fall, and we now have 15 > Oracle instances, with a mixture of 8.1.6 and 8.1.7, located there. We > recently have had 2 occurances of asynchronous I/O wait times exceeded. > When this occurs, every database crashes at the same time. The solution > from EMC is to turn asynchronous I/O off in all of the Oracle instances > (disk_async_io = false) and to increase the database writer slaves > (dbwr_io_slaves = <something not 0>) to emulate asynchronous I/O. > Has anyone run into this problem before? If so, how did you > "correct" it? My feeling is that EMC is trying to give us a bandage to > cover up the real problem, by trying to get Oracle to ignore it. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jeremiah Wilton INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
