Reinstallation Issues

[PCHomepage]

I had to reinstall Windows the other day and am getting the development server WAMP working again but have been having no end of trouble with MySQL. Apparently it saves two different copies of my.ini: one in the previous folder of the database folder and another in the installation folder. No matter what path I give it in the Workbench Server Administration to point to the existing databases, it wants to add a subfolder of "data" to it. When I look in the my.ini in the application folder, it has the correct path but nothing else; the copy if the database folder as the entire my.ini but has the /data/ appended to the path. It's like Workbench is saving one copy but MySQL is reading another.

Having said that and removing the improper folder name, it now sees the databases but two of them have the name prepended with #mysql50# even though it had before, and has now, v5.5 installed. How can I restore the proper names to these two databases? There are a number of databases but only two are misnamed in this way. It's not as though I'm a newbie - I've installed MySQL countless times in the past but never had such odd issues before.

Thank you!

 

[DonQuichote]

Does the error log say something? The funny names seem like error situations to me. Anyway, renaming and repairing should fix this. Off course, it is good to run ANALYZE TABLE on them first and run the backup.

+++ Despite being wrong in every important aspect, that is a very good analogy +++
Hex (in Darwin's Watch)

 

[PCHomepage]

That's a good question. Oddly, even though I installed only v 5.5, there are log files from last night in C:\ProgramData\MySQL\MySQL Server 5.1 but they appear to be in a binary format. There IS a folder for C:\ProgramData\MySQL\MySQL Server 5.5 but it shows logs from two days ago when I first tried installing v5.5 and the logs are also apparently binary. I don't even have a downloaded version of 5.1 but I noticed in my earlier attempts to install that a setting was looking in the v5.1 folder and had to be reselected to see the v5.5 folder.

These rather odd multiple locations for files seem to reflect the multiple my.ini locations so possibly there is a bug in the installer, perhaps something that wasn't updated from a previous version.

I just noticed that the Workbench Configuration File setting is pointing to C:\Program Files\MySQL\MySQL Server 5.5\my.ini but changing the my.ini there seems to do nothing while changing the copy that it created under the data folders does affect changes.