Bug #77594 Orphaned .frm after upgrade using MySQL Install Wizard renders database unusable
Submitted: 2 Jul 2015 8:27 Modified: 17 Jul 2015 9:31
Reporter: James Withers Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL for Windows: Installer Severity:S1 (Critical)
Version:5.6.25 OS:Windows (8.1 Pro x64)
Assigned to: CPU Architecture:Any

[2 Jul 2015 8:27] James Withers
Description:
After upgrading MySQL using the MySQL Install Wizard, I cannot access InnoDB tables and get the following error:

Cannot open table from the internal data dictionary of InnoDB though the .frm file for the table exists.

I also noticed all my user permissions had disappeared.

How to repeat:
Upgrade MySQL using the MySQL Install Wizard.

Suggested fix:
As per https://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html, the error is caused by an orphaned .frm file.

I suggest MySQL Install Wizard not do whatever it did to cause this problem.

How do I recover the data from this? .frm and .ibd files exist in the data/ directory.
[2 Jul 2015 8:30] James Withers
Additionally, trying to drop a database gives me "Error Code: 1010. Error dropping database (can't rmdir '.\b2b', errno: 41)"
[2 Jul 2015 10:53] Chiranjeevi Battula
Hello James Withers,

Thank you for the bug report.
Could you please provide repeatable test case (From & To versions) to confirm this issue at our end?

Thanks,
Chiranjeevi.
[2 Jul 2015 11:14] Chiranjeevi Battula
Hello James Withers,

Thank you for your feedback.
From which version(old version) to upgrading to new version(5.6.25).
To get MySQL version details manual:
https://dev.mysql.com/doc/refman/5.0/en/installation-version.html

Thanks,
Chiranjeevi.
[2 Jul 2015 12:57] James Withers
MySQL logs show it as 5.6.19
[3 Jul 2015 8:18] Chiranjeevi Battula
Hello James Withers,

Thank you for your feedback.
I could not repeat this issue at my end using Microsoft Windows (8.1 Pro x64) and MySQL upgrading form 5.6.19 to 5.6.25.
If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.
User manual for upgrading MySQL on Windows:
https://dev.mysql.com/doc/refman/5.6/en/windows-upgrading.html

Thanks,
Chiranjeevi.
[3 Jul 2015 8:20] Chiranjeevi Battula
screenshot

Attachment: 77594.zip (application/zip, text), 108.11 KiB.

[3 Jul 2015 8:23] James Withers
Did you add a database to the old version first, before performing the upgrade?
[3 Jul 2015 8:32] Chiranjeevi Battula
Yes James I have created database, tables and users with some permissions. It wouldn't giving any problem in upgraded version(5.6.25).
[3 Jul 2015 10:33] Chiranjeevi Battula
Hello James Withers,

Thank you for your feedback.
Could you please share us server error log and complete information, it may help us to confirm this issue at our end?

Thanks,
Chiranjeevi.
[10 Jul 2015 12:40] Chiranjeevi Battula
Hello James Withers,

Thank you for your feedback.
As per your server log ibdata1 file has deleted and it will generated new ibdata1 file which has no information about any tables and simple upgrade cannot cause such problems.

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.

Thanks,
Chiranjeevi.
[10 Jul 2015 12:53] James Withers
This is a bug: the idbdata file was deleted during upgrade.

Steps: 

1) Use Install Wizard
2) Upgrade MySQL
3) Find out ibdata file has been deleted.
[17 Jul 2015 8:13] Chiranjeevi Battula
Hello James Withers,

Thank you for your feedback.
I could not repeat this issue at my end using Microsoft Windows (8.1 Pro x64) and MySQL upgrading form 5.6.19 to 5.6.25.

Thanks,
Chiranjeevi.
[17 Jul 2015 8:13] Chiranjeevi Battula
screenshots

Attachment: 77594.zip (application/x-zip-compressed, text), 303.54 KiB.

[17 Jul 2015 9:31] James Withers
Is there any way to find out what may have caused the deletion?