RE: events to corrupt a database
- From: Josh Collier <Josh.Collier@xxxxxxxxxxxx>
- To: Martin Berger <martin.a.berger@xxxxxxxxx>
- Date: Tue, 13 May 2014 16:00:55 +0000
Hi Martin
The purpose is to break a database and then give it to someone else so they can
practice troubleshooting and recovery steps.
From: Martin Berger [mailto:martin.a.berger@xxxxxxxxx]
Sent: Monday, May 12, 2014 11:55 AM
To: Josh Collier
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: events to corrupt a database
I see it a hard task to corrupt a database at will. Especially if it is set up
properly :-)
It depends on the kind of corruption you want to achieve. For some small, but
very specific block corruptions I'd use BBED. Or I'd take a previous copy of
datafiles/redos and replace some blocks from the current files using dd.
But there are also some funny ways to confuse people: in a running DB, rename
any datafile and create a symlink with that name pointing to any other datafile.
It all depends on the type of corruption you want to create? what's the purpose
at all?
On Mon, May 12, 2014 at 8:16 PM, Josh Collier
<Josh.Collier@xxxxxxxxxxxx<mailto:Josh.Collier@xxxxxxxxxxxx>> wrote:
I am looking for different events to set that will corrupt a database, or mimic
a crash or error condition. For testing and training purposes? Any awesome ways
to break an oracle database beyond the standard “delete a live redo log”,
“delete a live datafile”, and “kill pmon”
Josh C.
Other related posts:
