Bug #17477 DB corrupted after a failed restart by configuration wizzard
Submitted: 16 Feb 2006 16:06 Modified: 16 Feb 2006 16:57
Reporter: [ name withheld ] Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.0 OS:Windows (Windows XP Por)
Assigned to: CPU Architecture:Any

[16 Feb 2006 16:06] [ name withheld ] 
Description:
After a successful install, configuration and test with two tables and 5 records in each, I wanted to reconfigure the erver using the wizzard. I added the TCP/IP capability.
At the end of the winzzard, it tryed to restart the server, but an error occured. (I don't remember).
I went in the Windows Services Window and I was unable to stop mySQL.
Afeter a restart, I was unable to restart MYSql server.
It says that the DB is corrupted.

I deleted the Dit of my DB and the data files ibdata1. MYSql Server starts, but I can't create tables:
ERROR 1005 (HY000): Can't create table '.\test\myTable.frm' (errno: 150)

I must reinstall all MySQL Server.

How to repeat:
Unable to repeat.

Suggested fix:
I'm afraid, no idea.
[16 Feb 2006 16:40] MySQL Verification Team 
We're sorry, but the bug system is not the appropriate forum for 
asking help on using MySQL products. Your problem is not the result 
of a bug.

Support on using our products is available both free in our forums
at http://forums.mysql.com and for a reasonable fee direct from our
skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Additional info:

If you1ve deleted the InnoDB table-space/log files then you need
to delete too the .frm files which were created before with the
InnoDB engine.
[16 Feb 2006 16:57] [ name withheld ] 
OK, stopping MYSql server that corrups the DB is not a bug ...