Page 1 of 1

Migrate existing installation from MySQL v3 to MySQL v5

Posted: Sun Mar 30, 2008 1:39 pm
by cmacneill
I have been happily using CMS Made Simple on my old server under MySQL v3.23.58 running on a Fedora Core 2 server with php v4.3. I am in the process of migrating to a new server running Ubuntu, MySQL v5.0.22-Debian_0ubuntu6.06.8 and php 4.4.2-1build1.

Both old and new systems are running Plesk, v8.2.1 on the old and v8.3 on the new.
Here's the information from version.php:-

$CMS_VERSION = "1.2.3";
$CMS_VERSION_NAME = "Black Rock";
$CMS_SCHEMA_VERSION = "29";

I've exported the old database using:-

mysqldump -uadmin -p`cat /etc/psa/.psa.shadow ` --add-drop-table --add-locks DATABASE_NAME > DATABASE_NAME_FILE

but I get an error when importing into the new database using:-

mysql -uadmin -p`cat /etc/psa/.psa.shadow` DATABASE_NAME < DATABASE_NAME_FILE

The dump and import commands are as recommended by my hosting centre.

The error is:-

ERROR 1071 (42000) at line 9953: Specified key was too long; max key length is 1000 bytes

Anyone got any idea what I need to do to successfully migrate the database?


Regards

Chris Macneill

Re: Migrate existing installation from MySQL v3 to MySQL v5

Posted: Sun Mar 30, 2008 2:50 pm
by alby
cmacneill wrote: ERROR 1071 (42000) at line 9953: Specified key was too long; max key length is 1000 bytes
Try to reduce varchar from 255 to 165

Alby

Re: Migrate existing installation from MySQL v3 to MySQL v5

Posted: Sun Mar 30, 2008 10:32 pm
by cmacneill
OK, found the varchar settings in the MySQL tables. Is it necessary to change all the varchar fields in all the tables? This could be a real pain!

Re: Migrate existing installation from MySQL v3 to MySQL v5

Posted: Sun Mar 30, 2008 10:53 pm
by Nullig
If you browse through the dump file to the line that had the error, you can see which table/field it choked on. Then just try changing that one.

Nullig

Re: Migrate existing installation from MySQL v3 to MySQL v5

Posted: Sun Mar 30, 2008 11:24 pm
by cmacneill
Many thanks, changing varchar(200) to varchar(165) in the CREATE for cms_xxxxxx_module_templates solved the problem, hopefully it won't any other problems doing this.


Regards

Chris Macneill