this would occur on any storage IMHO. if your filesystem is 100% full it cannot write to it and if that filesystem contains things like redo logs, archive logs, and/or system tables generally bad things occur.
my first question would be why are they reaching 100% and do you have any filesystem monitoring in place? there is no reason your oracle filesystems should be reaching 100%
to me this is not a netapp/nfs issue but an operations issue--it would occur on nfs, san, or local disk.
--daniel
--
Daniel Leeds
Manager, Storage Operations
Edmunds, Inc.
1620 26th Street, Suite 400 South
Santa Monica, CA 90404
310-309-4999 desk
310-430-0536 cell
-----Original Message-----
From: owner-toasters@mathworks.com on behalf of Li, Jackie (Yanhui)
Sent: Fri 12/5/2008 10:33 AM
To: toasters@mathworks.com
Subject: oracle coruption caused by NFS file system is full
Our firm runs oracle 9i using NFS file system from Netapp(3040 running 7.2), we have noticed few cases now that when the NFS file system is full, oracle database crash and can not even start after that.
It turns out that database has logical corruption, does anybody experience similar issues?
Thanks