Bug #16989 mysqlcheck doesn't finish it's job if DB deleted after it started
Submitted: 31 Jan 2006 23:03 Modified: 31 Jan 2006 23:57
Reporter: Alexey Polyakov Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.16, probably affects other versions OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[31 Jan 2006 23:03] Alexey Polyakov 
Description:
When I run mysqlcheck -r -A, and one of databases gets deleted during the process, I get message like this:
mysqlcheck: Got error: 1049: Unknown database 'ozan_nuke1' when selecting the database
and mysqlcheck stops working.

How to repeat:
Run mysqlcheck -r -A and deleted some database before it finishes.

Suggested fix:
Make mysqlcheck ignore error 1049 and proceed to next database.
[31 Jan 2006 23:34] Hartmut Holzgraefe 
did you try the --force option?
[31 Jan 2006 23:51] Alexey Polyakov 
Ah, sorry for wasting your time. Works fine with --force.
Please delete this report.