Comments on: MyISAM table incompatibility when upgrading to 5.1 http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/ Everything In Life Is Random! (Personal and Work) Thu, 02 Feb 2012 16:29:39 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Miki http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/comment-page-1/#comment-4313 Miki Fri, 06 Jun 2008 11:50:59 +0000 http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/#comment-4313 Hi Venu, I have similar problem. I should transfer my databases from old to new data server. Its on FreeBSD and I installed in from th ports. On my old data server I have server version: 4.1.18 and on new mysql-server-5.1.24_1. Whenever I try to transfer db from one to another, after I do myisamchk --safe-recover of all my tables in all my databases, I still get ERROR 1034 (HY000): Incorrect key file for table 'radacct'; try to repair it mysql> repair table radacct; +--------------+--------+----------+----------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +--------------+--------+----------+----------------------------------------------------------+ | rudb.radacct | repair | Error | Incorrect key file for table 'radacct'; try to repair it | | rudb.radacct | repair | error | Corrupt | +--------------+--------+----------+----------------------------------------------------------+ 2 rows in set (0.00 sec) What should I do? Hi Venu, I have similar problem. I should transfer my databases from old to new data server. Its on FreeBSD and I installed in from th ports. On my old data server I have server version: 4.1.18 and on new mysql-server-5.1.24_1. Whenever I try to transfer db from one to another, after I do myisamchk –safe-recover of all my tables in all my databases, I still get

ERROR 1034 (HY000): Incorrect key file for table ‘radacct’; try to repair it
mysql> repair table radacct;
+————–+——–+———-+———————————————————-+
| Table | Op | Msg_type | Msg_text |
+————–+——–+———-+———————————————————-+
| rudb.radacct | repair | Error | Incorrect key file for table ‘radacct’; try to repair it |
| rudb.radacct | repair | error | Corrupt |
+————–+——–+———-+———————————————————-+
2 rows in set (0.00 sec)

What should I do?

]]> By: Venu Anuganti Blog » MySQL MyISAM and Merge Tables Incompatibility - II http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/comment-page-1/#comment-1779 Venu Anuganti Blog » MySQL MyISAM and Merge Tables Incompatibility - II Sat, 09 Feb 2008 07:22:11 +0000 http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/#comment-1779 [...] months back we noticed the incompatibility change related to MyISAM that was introduced in recent 4.1.23 and 5.0 and 5.1 which breaks when one wants to upgrade to [...] [...] months back we noticed the incompatibility change related to MyISAM that was introduced in recent 4.1.23 and 5.0 and 5.1 which breaks when one wants to upgrade to [...]

]]> By: Venu Anuganti http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/comment-page-1/#comment-743 Venu Anuganti Tue, 02 Oct 2007 16:19:00 +0000 http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/#comment-743 Thanks Sinisa :) Good to catch you..you never change :) Thanks Sinisa :) Good to catch you..you never change :)

]]> By: Sinisa Milivojevic http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/comment-page-1/#comment-742 Sinisa Milivojevic Tue, 02 Oct 2007 13:21:50 +0000 http://venublog.com/2007/10/01/myisam-table-incompatibility-when-upgrading-to-51/#comment-742 Venu, my dear friend, This is not necessarily a bug. This could be just a consequence of how 4.1 and 5.0 are treating end spaces. As our manual says loud and clear, please dump / restore when upgrading from 4.1 to 5.0. You can't upgrade any other way. Venu, my dear friend,

This is not necessarily a bug. This could be just a consequence of how 4.1 and 5.0 are treating end spaces. As our manual says loud and clear, please dump / restore when upgrading from 4.1 to 5.0. You can’t upgrade any other way.

]]>