MySQL help

I have been googling for 4 hours now to no avail.

Fireman!

I'm unable to see all of that link Ron as I appear to be trapped in community classic and the end of it just appears as a series of dots.

When I upgraded, the existing database files were found automatically.
I left things alone and it all worked. You still have a 5.1 database that is now being operated on by a 5.5 engine. Only when you make a brand new database will it be a 5.5 database version.
Perhaps your moving the link files has now confused the install and it cannot find the new procedure versions etc

Thanks cornubia. Was your old data not in e.g. c:/ProgramData/MySQL/MySQL Server 5.1/data whereas the upgraded programme's data was in c:/ProgramData/MySQL Server 5.5/data?

Did you uninstall the old version first? If not, maybe that was where I went wrong.

Feck, it may be too late now, but you should be able to find instructions on upgrading from 5.1 to 5.5 in a .pdf file that should have downloaded with your 5.5 installation pack.

The .pdf is called refman-5.5-en.a4.pdf an it's in MySQL\MySQL Documentation 5.5.17\

One thing the manual is very particular about is

Before upgrading a MySQL service from MySQL 5.1 to 5.5, you should stop the 5.1 server and remove the instance. Run the
MySQL Instance Configuration Wizard, choose the Remove Instance option and in the next screen, confirm removal. After
that it is safe to uninstall MySQL Server 5.1.

When I upgraded I must have just got lucky and stopped the service by a fluke, but perhaps you might just get away with stopping the server anyway (whichever version it thinks it's running, and then running the 5.5 installer again?

Thanks Gus, but it is too late. On top of my other problems I was getting bad handshake errors within c++ builder which (via googling) meant I was going to have to upgrade my Devart MyDAC components and I couldn't be bothered doing that without knowing if I could retrieve the procedures and functions. I finally found where they were stored (in the data folder there's a folder called MySQL which contains a Proc and Func table) but copying them to the 5.5 folder didn't work as I got a corrupted file message for both. I suspect those tables needed passing to the mysql_upgrade utility (I think the .sym links meant my other tables were upgraded when I ran that utility) but by then I was demented and uninstalled the lot. I'm now back at my original configuration and everything's working as was.

As I uninstalled the previous version of MySQL before attempting the upgrade I take it my server instance was already removed but I don't know if uninstalling everything was the right move. Maybe if I hadn't it would've recognised the old data and upgraded it automatically. It's all in keeping with past upgrades. I don't recall ever having an easy installation. I'll bet you that pdf file would make your head burstjust reading it?

One alternative might be to go back to a Restore point, before you started trying to upgrade and start over again, this tme stopping the 5.1 service before upgrading (and even reading the manual first ... no criticism implied ... i'm a guesser too)?

I'll leave it till after the flat before I try again gus. I lost a whole day of programming yesterday. I take it you didn't uninstall the old version? Does it say anything in the manual about that?

gus, could you also check your c:/programdata/MySQL/MySQL Server 5.x folder and see what's in them? After my upgrade the old 5.1 folder was still there with the old data folder intact. The 5.5 folder's data folder was obviously created anew and I had to copy my old .sym files to that before the server recognised any data.

i'm pretty sure you do have to uninstall 5.1.x before upgrading t0 5.5.x

The manual says:

The MySQL Installation Wizard can perform server upgrades automatically using the upgrade capabilities of MSI. That means you
do not need to remove a previous installation manually before installing a new release. The installer automatically shuts down and
removes the previous MySQL service before installing the new version.
Automatic upgrades are available only when upgrading between installations that have the same major and minor version numbers.
For example, you can upgrade automatically from MySQL 5.5.5 to MySQL 5.5.6, but not from MySQL 5.1 to MySQL 5.5.See Section 2.3.8, “Upgrading MySQL on Windows” (2.3.8 is the bit where the quote about stopping the service etc comes from).

To be honest I can't remember what steps I went through when upgrading ... i had my eyes closed in prayer most of the time.

i had my eyes closed in prayer most of the time.

That's a good summing up of the procedure gus. Thanks for your help.

the old data files from my 5.1.x installation seem to have been transferred automatically to the 5.5.x data directory ... i certainly didn't do it.

I'm on Wndows7 and I  chose not install to either of the Program Files directories ('Program Files(x86)' ... which is for 32 bit programmes or 'Program Files', which is for 64 bit programmes), but simply installed to the C:\ drive, so I actually have 3 MySQL folders, one at each of those locations, but the on at C:\ is the one with the data files ... dunno what the other are for, to be honest i suspect they're redundant.

I always install any programs that i may need to configure manually straight to the C:\ drive, to avoid fannying about with administrator/user permissions, which Win7 is a bu$$er for.

Sorry if that creates even more confusion, but that's what i did and it does work for me.

Were you going from 5.1 to 5.6 or just next one up?

*5.5

5.1.x ( x meaning some number i can't remember) to 5.5

but I only had one database that was moved from 5.1.x to the 5.5 version during the install, and it is only data ... no stored procedures or other fancy stuff ...

i had to reconstruct some others from another pc by getting the old ones to export  'CREATE TABLE' queries and then running those queries on the new (5.5) dbase ... there's probably a smarter way of doing it over a network, but exporting/importing was actually a relatively painless process.

gus, do you know anything about server instances and connections. I'm guessing as I'm the only one using the server I only need one instance of the server running but, within my c++ builder application, I need a different TMyConnection for each programme thread. Does that sound right?

For server read local server.

Whatever happened to forum.bdp.betfair.com?

We don't want to put too much technie stuff on here and scare off the punters who just signed up for their £25 bonus during Grand National weekend.

sorry feck I dunno anything about c++ or server instances ... databases and i have a strictly 'need to know' relationship.

i do have a Java program that uses one of the MySQL databases, but it only connects to the dbase on a single thread (it only needs to read from the dbase, not write) and when it connects it uses methods in a Java Class that's a 'black box' to me.

DivideByZeroError is probably right, you'd likely stand a better chance of finding a c++ (and MySQL) whizz on the bdp forum:


http://forum.bdp.betfair.com/

OK, thanks for your help gus.

gus, I was given this advice but haven't retried yet. It might be worth storing it for next time.


Upgrade guide.
http://dev.mysql.com/doc/refman/5.5/en/upgrading-from-previous-series.html

Upgrade Mysql 5.1 to 5.5.
MySQL 5.5 binaries install to different folder. Your old my.ini file is left intact in it's old location.
In Win 7 your MySQL 5.1 data folder was, by default in C:\ProgramData\MySQL\MySQL Server 5.1\data.

Your new MySQL data folder is in C:\ProgramData\MySQL\MySQL Server 5.5\Data

Your Procedures and Functions, as you've discovered are stored in the MySQL database.
So, after you upgrade, strop the service, and then you can either

A. Edit your new my.ini to point to the old MySQL 5.1 data folder, ensuring the size of ib_logfiles specified in the new my.ini is the same as specified in the old my.ini. Start the server. You'll get warnings about missing tables, and a direction to run mysql_ugrade. Do that to upgrade the V5.1 MySQL database to V5.5.

This option has the potential to destroy your old database.

Or
B. Copy the old 5.1 data folder over the new 5.5 data folder. Edit my.ini ib_logfile size. Start the server, then run mysql_upgrade.

This option keeps your old database as a backup.

Alternatively, take a backup of your old database(s) including mysql
at V.5.1, do the upgrade.
Restore the backup, including MySQL
Run mysql_upgrade.

thanks Feck ... now you mention it I do vaguely remember some mucking about with the .ini file, but I was just following instructions on some website idiots guide to MySql. Whatever it was it worked so i instantly forgot it!

I doubt I'll ever upgrade to a later version, because, come to think of it, version 5.5 does nothing for me that wasn't done just as well as 5.1, and I can't visualise any way that a future version would handle my stuff any better.

Do you think you really need to upgrade?

gus, When I alter a table in 5.1 (e.g. delete a column) the information schema still shows the column as being there. My c++ builder programme makes use of the information schema and the only way I can get it to show the correct columns is to reboot. I'm hoping 5.5 will have corrected that but I can't be sure till I do it. I'll leave it till I've more time though.