I checked now and saw that they have already attempted a restore
previously and hence the original table was dropped and recreated.

    I found some links on the internet stating that after restoring the
dump file to the new version, the proc table should be dumped using the
new version and reloaded.

     After this a mysql_upgrade needs to be run.

        I am however not sure how valid this is or whether this is
really a solution.

        I am able to drop the database and reload the mysql to get the
original proc table again, however how would I fix the column problem
then?

        The current proc tables have 16 columns.


            Any ideas?

Regards
Machiel

-----Original Message-----
From: partha sarathy <par...@mafiree.com>
To: Machiel Richards <machi...@rdc.co.za>, mysql mailing list
<mysql@lists.mysql.com>
Subject: Re: MySQL restore failing
Date: Fri, 3 Dec 2010 14:02:59 +0530 (IST)


In mysql 5.1, mysql.proc table contains 20 columns. Can you check your new DB 
again?

-Partha



----- Original Message ----
From: Machiel Richards <machi...@rdc.co.za>
To: mysql mailing list <mysql@lists.mysql.com>
Sent: Fri, 3 December, 2010 1:38:24 PM
Subject: MySQL restore failing

Hi All

        I am hoping that someone could assist me with this one.

        I am trying to restore a database to a new machine for testing
purposes.

        The current machine is running mysql-5.0.72sp1 and the new
machine 5.1.50.

        When running the restore is runs for quite a while and then
crashes with the following message:



                        [r...@mysql2 home]# mysql -u root -p <
                        mysql_full_021210.dump
                        Enter password: 
                        ERROR 1547 (HY000) at line 14284: Column count
                        of mysql.proc is wrong. Expected 20, found 16.
                        The table is probably corrupted


        I have checked the current production system for this table and
the column count is 16, I then checked the new system as well as a newly
setup clean MySQL-5.1.50 database and they are all 16 columns and
exactly the same as far as I can see.

        Is there anyone that might know why I am getting this?

        I would really apprecaite any help as this machine needs to be
up and running by eod today.

Regards
Machiel

Reply via email to