you should enable the auto-repair feature on the mysql configuration so that those damaged files will be repaired automatically.
replicating the report is one thing while replicating the report generation process is another. TWG should also be conducting failover simulations by now since your local election is near. and please note, off-shore replicators might even cause a DoS on the main host especially if the main node is weak and the replicators are way too much aggressive. there should be some guidelines for those who wish to mirror the data. On 2/10/07, Roberto Verzola <[EMAIL PROTECTED]> wrote:
On Saturday 10 February 2007 7:23 pm, Orlando Andico wrote: > welcome to the craptacular world of MySQL :P > try an isamchk or myisamchk that usually can recover something from > the crap that MySQL leaves behind... Yes, I did use mysqlcheck -r and the files were craptacularly repaired... We're back in business. It really must have been the power outage then. Well, at least the solution is quite simple. I was concerned it was something more complicated or sinister. Greetings, and thank you, all thosewho sent in their advice. Obet
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
