It certainly seems that 5.0.44 and 5.0.45 are unstable. I have logged
this as bug http://bugs.mysql.com/bug.php?id=31008
A 64-bit Gentoo Linux box had just been upgraded from MySQL 4.1 to
5.0.44 fresh (by dumping in 4.1 and restoring in 5.0.44) and almost
immediately after that, during which t
Thank you for your replies. I attempted to restore again and most
oddly, mysql complained that it couldn't restore to a particular
table because it wasn't in the database, which, of course, it had to
be because the restore itself had just recreated it. So I blew away
the entire mysql directory
The checksum errors might be due to various reasons. We had similar issue
where we restored the database multiple times, replaced the ram sticks
nothing helped. Finally we drilled down the issue to the chassis. Recommend
testing the restore on a different machine to rule out any hardware issue.
--
Hi
This might be happening due to two reasons;
1 The system date might not be correct.
2. Some things wrong with log postion (Incorrect log position)
Regards,
Krishna Chandra Prajapati
On 8/31/07, Maurice Volaski <[EMAIL PROTECTED]> wrote:
>
> A 64-bit Gentoo Linux box had just been upgraded from
