Comment 2 for bug 1324295
Revision history for this message
| Valerii Kravchuk (valerii-kravchuk) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I see the same error messages with upstream 5.6.17 on Windows:
2014-05-18 17:46:30 5396 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: ready for connections.
Version: '5.6.17-log' socket: '' port: 3314 MySQL Community Server (GPL)
2014-05-29 09:30:15 5396 [ERROR] Table .\test\sometable has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
2014-05-29 09:30:15 5396 [Warning] Table .\test\sometable key_used_on_scan is 0 even though there is no primary key inside InnoDB.
2014-05-29 09:30:15 5396 [ERROR] Index key1 of test/sometable has 2 columns unique inside InnoDB, but MySQL is asking statistics for 3 columns. Have you mixed up .frm files from different installations? See http://
2014-05-29 09:30:15 5396 [ERROR] Index key2 of test/sometable has 2 columns unique inside InnoDB, but MySQL is asking statistics for 3 columns. Have you mixed up .frm files from different installations? See http://
2014-05-29 09:30:15 5396 [ERROR] Index key3 of test/sometable has 2 columns unique inside InnoDB, but MySQL is asking statistics for 3 columns. Have you mixed up .frm files from different installations? See http://
and server seems to hang for SELECT and even crash there when running EXPLAIN SELECT ...
So, I think this is upstream MySQL bug. Will you report it to http://