Q&A

Q1:When I run a query, I'm getting a message from MySQL like “Got Error 127 from table handler.” Is my database corrupted?
A1: Probably yes. But don't panic: Use myisamchk to check the table you suspect is corrupted without options and then using the -q, -m, and perhaps -e options. You can also add a -i for more information.

Ideally you should shut down mysqld, or at least flush tables and try to ensure that myisamchk is the only thing accessing a table; otherwise, it might tell you that a table is corrupt when it isn't.

If a problem is confirmed by any of these checks, commence the procedure outlined earlier for repairs.

Q2:How can I find out more about these errors from the table handler?
A2: If you're getting an error number, you can look it up using perror. For example:
# perror 126
Error code 126:  Unknown error 126
126 = Index file is crashed / Wrong file format

Q3:Can doing a table repair make the situation worse?
A3: It is possible for corruption to be made worse if other clients are using the table while you're running myisamchk. You should shut down the MySQL server while you're doing the repair, or failing this, flush tables so that they're saved to disk; then make absolutely sure that no other clients are accessing the table while you perform the repair.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.15.3.167