On Sun, Apr 18, 2010 at 10:39 AM, Suresh Kuna <sureshkumarilu@stripped> wrote:
> open the file and remove some data and close it for both data file and index
> files, So the tables will be corrupted when access.
> On Sun, Apr 18, 2010 at 9:55 PM, Nurudin Javeri <nsjaveri@stripped> wrote:
>> Hi all, I am hiring a few new junior DBA's and I want to put them thru a
>> simple db repair training. Does anyone know how I can deliberately corrupt
>> a MyISAM and InnoDB database in different ways please? So what I want to
>> is corrupt 3 MyISAM 100gb databases, 3 InnoDB 100gb databases - ALL WITH
>> DIFFERENT ERROR MESSAGES and have these newbies fix them in a 2 hour period
>> :-) I have fixed oodles of db's but NEVER thought I would see the say
>> I would WANT to corrupt a db on purpose, but that day is here and am looking
>> for advise please.
Umm, shouldn't you train your Junion DBA to:
1. fail off of the corrupted servers.
2. restore from backup.
3. or at least get a non-junior dba and then have them shadow?
I have a problem with the idea of "repairing" Innodb. Depending on
where the corruption (checksum mismatch) has occurred it can be very
difficult to get all the original data out. Don't get me wrong, there
are way to do it, but it is a nasty endeavor.
For that mater I don't trust "repairing" MyISAM all that much either.
I try my very best to keep MyISAM out of production. In my opinion
MyISAM should be treated as something one step higher than the
blackhole engine. Put data in and you might be able to pull it out
later. (don't get me wrong, packed myisam has its place...)