RE: Accidentally Delete *.dbf Files, OH NO!!!

From: "Mark W. Farnham" <mwf@xxxxxxxx>
To: <mfontana@xxxxxxxxx>, <Oracle-L@xxxxxxxxxxxxx>
Date: Tue, 1 Feb 2005 17:02:12 -0500

Obviously your SA is voting that you should use raw partitions instead of
file system files. Of course then the nefarious forces in opposition to
using raw will respond by dd'ing backups in the wrong direction and copy the
contents of some recycled tape over the top of your data.

Root users tend to be able to circumvent any prophylaxis. Various alias
replacements for the usual rm have been suggested, but of course the
administrator will know where the "REAL" rm lives and will use it when
cleaning up to avoid the hassle of being told not to delete files that look
like good solutions to the space problem. (Or, more legitimately: When they
inadvertantly cd to the wrong whole directory they mean to delete from and
intentionally use the rm normal version to delete *.dbf, everything goes
poof).

I'm not saying it is hopeless, but a creative lunatic with root authority is
nearly impossible to stop.

Good luck!

mwf

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Michael Fontana
Sent: Monday, January 31, 2005 6:23 PM
To: Oracle-L@xxxxxxxxxxxxx
Subject: Accidentally Delete *.dbf Files, OH NO!!!



I have been working with Solaris for several years now.  We have had a rare
but particularly debilitating problem where certain people who will remain
nameless, in an effort to "clean up" disk space, have nailed a .dbf file or
two.  I know I should have the solution to this on close at hand, but I seem
to recall this was difficult, if not impossible, on other Unix platforms
(such as AIX), because the file would be "locked" or "in use", and the
nefarious "rm" command would fail.  Alas, Solaris is all too willing to
comply when asked.

Is there something that can be done, at the OS or Oracle level, to prevent
such a thing?  Needless to say, the "whackers" are using root to enter the
command, so changing permissions would accomplish little.  They are already
set to only allow "oracle" write access.

Any help or even ridiculing chuckles and admonitions would be greatly
appreciated.



--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l

RE: Accidentally Delete *.dbf Files, OH NO!!!

Other related posts: