I found that the database I was primarily interested in only had a
MyISAM table (.myd and .myi file), nothing in InnoDB. So I first copied
over that database directory to my other MySQL instance and restarted
it. MySQL Workbench hang a bit when expanding its tree, so I dropped the
database, recreat
Hah. I suspect the machine was running when it crashed - that is, the mysql was
shut down uncleanly?
You can safely ignore the mysql.plugin bit for the moment - that's for when
it's booted properly. It looks like the newer InnoDB has trouble reading your
ibdata file. Possible causes:
* Are all
On 09.11.2011 21:58 CE(S)T, Reindl Harald wrote:
> Am 09.11.2011 21:46, schrieb Yves Goergen:
>> The old machine was an unknown MySQL version on Windows XP
>
> pfff - unknown version? how comes?
The old MySQL installation doesn't run anymore because the OS is gone. I
could only backup the files.
Am 09.11.2011 21:46, schrieb Yves Goergen:
> The old machine was an unknown MySQL version on Windows XP
pfff - unknown version? how comes?
> The error log is attached to this mail. It all sounds like real bugs in
> MySQL, at least it's standing in the file
there is no attachment
so please CLEA
Hi,
Recently a home server has crashed and would not boot anymore into
Windows. We decided to replace it altogether and I managed to repair the
file system more or less so that I could copy some directories from the
broken disk. One of them is the MySQL data directory of that XAMPP
installation.
