Re: How does one manually corrupt a database (database file, redo logs and backups)

  • From: "LS Cheng" <exriscer@xxxxxxxxx>
  • To: "Charles Schultz" <sacrophyte@xxxxxxxxx>
  • Date: Sat, 2 Sep 2006 17:58:10 +0200

have you tried with an hex editor?

On 9/2/06, Charles Schultz <sacrophyte@xxxxxxxxx> wrote:

That does not help much. If it is undocumented and you do not tell me how to use it, I am kinda stuck at square one, nu? =)


On 9/2/06, LS Cheng < exriscer@xxxxxxxxx> wrote: > > hi > > you can use bbed, its an undocumentated executable though > > > On 9/2/06, Charles Schultz <sacrophyte@xxxxxxxxx > wrote: > > > > Funny topic, eh? I am practicing backup and recovery procedures and > > finding that recovery is quite easy since I never have corrupted blocks to > > worry about. So, how do I practice for a "worse case" scenarios? Are there > > white papers out there that go over this kind of stuff? I found several > > "Best Practices" in metalink (look Mladen, not plural), but that is not > > exactly what I am looking for as they tell you how to fix the problem, not > > make the problem. I have tried overwriting the binary files, but being > > simpled-minded I was using vi. I thought about using the unix dd utility - > > unfortuantely I do not have enough experience to be surgical (easy to mess > > up the first few blocks, but what about the middle?). Can I use the same > > method to isolate corruption to various parts of the database (ie, database > > files, redo logs or rman backups)? > > > > I have a gut feeling that someone has already documented this, so if > > this is the case, please point me there. > > Thanks, > > > > PS - I have been practicing on 9iR2. Yet anything above 9iR1 would be > > fine. > > > > -- > > > > Charles Schultz > > > >


--

Charles Schultz

Other related posts: