This is also why you don’t enable
autoextend on tablespaces, and put your archive logs on a separate filesystem. Space
management is part of the day to day responsibility of a DBA. Running out of
space is a Very Bad Thing for databases.
Thanks,
Matt
From:
owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Glenn Dekhayser
Sent: Monday, December 08, 2008
1:49 PM
To: Li, Jackie (Yanhui);
toasters@mathworks.com
Subject: RE: oracle coruption
caused by NFS file system is full
Just because the
database *may* start up OK after
such an event, by no means should you assume that it *should* start up OK. The ability to
come back up is completely dependent upon what state the database was in (where
it was in transactions, etc) when the filesystem filled up. The more
active the database was when the filesystem choked, the higher likely you’ll
have corruption that you can’t recover from.
I completely agree
with the assessments of everyone else on the list- NEVER let your filesystem
fill up.
That being said- you
should look at the volume “auto grow” which will (sorry)
automatically grow the volume when it hits certain thresholds. Could
prevent disaster in the future.
Glenn
Dekhayser
VoyantStrategies
From:
owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Li, Jackie (Yanhui)
Sent: Friday, December 05, 2008
2:50 PM
To: Leeds, Daniel;
toasters@mathworks.com
Subject: RE: oracle coruption
caused by NFS file system is full
We had experience with SAN attached
device, normally the database will just start fine after you increase the file
system capacity.
From: Leeds, Daniel
[mailto:dleeds@edmunds.com]
Sent: Friday, December 05, 2008
11:35 AM
To: Li, Jackie (Yanhui);
toasters@mathworks.com
Subject: RE: oracle coruption
caused by NFS file system is full
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.
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