bad data in mysql tables in replication server

[Luc Foisy]

Last week many of our server and client servers had a power problem. Not =
quite sure how the servers were handled, wasn't on site, but I don't =
think some of these servers got shut down gracefully. but anyways that =
shouldn't matter to my question

I ran myisamchk on the data directories and I get a large report =
containing things such as

myisamchk: MyISAM file /usr/data/mysql/qbslive/MANIFESTSPOOL.MYI
myisamchk: warning: 1 clients is using or hasn't closed the table =
properly
MyISAM-table '/usr/data/mysql/qbslive/MANIFESTSPOOL.MYI' is usable but =
should be fixed
myisamchk: MyISAM file /usr/data/mysql/qbslive/MARKETING.MYI
myisamchk: warning: 1 clients is using or hasn't closed the table =
properly
MyISAM-table '/usr/data/mysql/qbslive/MARKETING.MYI' is usable but =
should be fixed
myisamchk: MyISAM file /usr/data/mysql/qbslive/ORDERHEADER.MYI
myisamchk: warning: 1 clients is using or hasn't closed the table =
properly
MyISAM-table '/usr/data/mysql/qbslive/ORDERHEADER.MYI' is usable but =
should be fixed

I am assuming I can just run myisamchk -r on these tables to fix them up =
on the master server... but I have multiple replication servers of =
databases...
Can I repair these in the same way, or will the system fix it up or =
what? The slave servers are definately not running at the moment, have =
show slave status on one rep server of=20
| 1062 | error 'Duplicate entry '5486435' for key 1' on query =
'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())' |

Not quite sure what to do here, is my replicant toast?

Luc Foisy=20
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw