On Thu, May 10, 2012 at 10:26 PM, Steven Staples sstap...@mnsi.net wrote:
I think you can scan the syslog for the mysql daemon, and it will show you
any crashed, or problematic tables?
If this is in fact the case, you could try that, and then run though the
tables to check them later?
Much faster: SHOW TABLE STATUS -- It will have NULLs for the tables that
really need REPAIR. (Those that were not properly closed don't have to be
REPAIRed.)
If you system is new enough, you can find the list of databases (TABLE_SCHEMA)
from `information_schema`.
In the long run, consider
You can enable check/recovery automatically by using myisam_recover. Look it
up in the documentation.
There is no way to repair them faster, though.
On May 10, 2012, at 2:40 PM, Adrian Fita wrote:
Hi.
I have several hundreds of databases with MyISAM tables in a server and
after a power
On 10/05/12 21:51, Mihail Manolov wrote:
You can enable check/recovery automatically by using
myisam_recover. Look it up in the documentation.
There is no way to repair them faster, though.
Thanks for the quick response. This definetly looks like a useable
solution. Do you know if during the
AFAIK the tables will be locked one by one until checked/repaired.
On May 10, 2012, at 3:07 PM, Adrian Fita wrote:
On 10/05/12 21:51, Mihail Manolov wrote:
You can enable check/recovery automatically by using
myisam_recover. Look it up in the documentation.
There is no way to repair them
AFAIK the tables will be locked one by one until checked/repaired.
On May 10, 2012, at 3:07 PM, Adrian Fita wrote:
On 10/05/12 21:51, Mihail Manolov wrote:
You can enable check/recovery automatically by using
myisam_recover. Look it up in the documentation.
There is no way to
