RE: database decommission checklist

From: QuijadaReina, Julio C <>
Date: Tue, 30 Jun 2009 11:11:48 -0400
Message-ID: <>

Life catches up with characters like Madoff sooner or later. Unless one lives as a hermit, tracks are hard to cover. And it usually takes more than erasing what's on a disk to cover them ;-)


From: Howard Latham [] Sent: Tuesday, June 30, 2009 9:56 AM
To: QuijadaReina, Julio C
Cc:;;; Subject: Re: database decommission checklist

You really think one write to a disk is enough - Well so long as you aren't Dexter or Madoff! 2009/6/30 QuijadaReina, Julio C <<>>

On Linux, you can use a tool called 'shred'. It will repeatedly write 25 times over on the disk. Make it a little harder to recover data if that is your intent.


From:<> [<>] On Behalf Of Bobak, Mark

Sent: Friday, June 26, 2009 5:40 PM

Subject: RE: database decommission checklist

And, might I add, when it comes to wiping the disk, one good wipe is all it takes, contrary to what government standards say.....

I challenge anyone to recover data from a disk after a single pass of:

dd if=/dev/zero of=/dev/sd0

You do that, the data is gone, and it's not coming back....


From:<> [<>] On Behalf Of Allen, Brandon Sent: Friday, June 26, 2009 4:42 PM
To:<>;<> Subject: RE: database decommission checklist

I would just add wiping the disk, or taking a sledgehammer to it if it's really sensitive data and you'll be decommissioning the hardware too, and then other little things like updating documentation and maybe any clients, e.g. tnsnames.ora files, that need to be updated.



Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.


Howard A. Latham

-- Received on Tue Jun 30 2009 - 10:11:48 CDT

Original text of this message