What if the DBA ask for the backup? And those recommendations can be "fixed" or they have a very high chance of making recovery impossible?
On Sun, Apr 18, 2010 at 1:09 PM, Rob Wultsch <wult...@gmail.com> wrote: > On Sun, Apr 18, 2010 at 10:39 AM, Suresh Kuna <sureshkumar...@gmail.com> > 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 <nsjav...@idh.com> > 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 do > >> 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 > where > >> I would WANT to corrupt a db on purpose, but that day is here and am > looking > >> for advise please. > >> > >> Thanks... > >> > >> Nunu > >> > > 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...) > > -- > Rob Wultsch > wult...@gmail.com > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=mr.crip...@gmail.com > >
