Ian, Friday, July 05, 2002, 4:11:37 PM, you wrote: IH> Every time we move our database onto new hardware (ie. Pentium 4) we get IH> errors 127 and 134 within the mysql error logfile. When we then run the IH> check (i.e. CHECK TABLE tablename EXTENDED) on the databases the status IH> comes back as being OK. Should we believe this, or do we still need to run IH> the repair ? IH> We are currently running RedHat 7.2 (kernel 2.4.16) with MySQL 3.2.49
1. Are you sure that you checked an appropriate table, i.e. that was crushed? 2. In some cases CHECK TABLE call REPAIR ... If error doesn't occur after CHECK TABLE it not necessary to run REPAIR TABLE... -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
