Error restoring tables using migrate

Hi Rob,

Thanks for the purchase!

The problem is that the MySQL server on the ‘old’ site hosting is producing output that is not accepted by the MySQL server on the ‘new’ side. i.e. They either they are different versions, and sufficiently different that their output is mutually incompatible, or they are similar versions but (I think this is more likely, looking at your info) the ‘new’ side has functionality missing that the ‘old’ side was using.

This is easily fixable, so don’t worry! We may just need a few goes to find out exactly which bit it does not like.

Firstly – are you able to find out the MySQL versions on both sides? In UpdraftPlus, scroll down to the “Show expert settings” link, and click it. Then scroll down again, and find the “show PHP information (phpinfo)” link and click that. In the dialog that opens, search for “Client API library version”, and note the version number. Do this on both ‘old’ and ‘new’ sites. This information will help us to automate the next step for the future.

Secondly, to fix the actual problem. The db.gz file that is your database backup needs to have a search-and-replace done upon it by hand. Either email it to us, or

1) decompress it (using https://7-zip.org) open it up in a text editor.

2) experiment with editing (via search-and-replace) every CREATE TABLE statement (it sounds like there are 21). This will be the problematic bit:

ENGINE=Aria AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 PAGE_CHECKSUM=1;

Likely problems are that:
i) Your new server supports TYPE=Aria instead of ENGINE=Aria.
ii) Your new server does not have the Aria engine at all – replace “ENGINE=Aria” with “Engine=MyISAM” and remove “PAGE_CHECKSUM=1”.

ii) is the much more likely one, as Aria is a not very widespread engine. So try that first unless you’re confident that your new server has the Aria engine.

Then,

3) Re-compress the database file so that it is again a db.gz file.

4) You can now use your altered file for the migration.

If you have any trouble, then just email the db.gz file to [email protected], and we’ll alter it for you.

Best wishes,
David

Hi David

Thanks for the comprehensive answer :

Old Client API library version : mysqlnd 5.0.10 – 20111026 – $Id: e707c415db32080b3752b232487a435ee0372157 $
New Client API library version : 5.1.66

I have emailed the db.gz file to you to have a look at.

I will be needing to do this quite a bit in the next few weeks, so would really appreciate if we could automate the process.

Thanks and regards
Rob

Hi Rob,

I’ve emailed you now with the development version of UpdraftPlus + Migrator, which now handles this situation. The problem was the PAGE_CHECKSUM=1 part of the “CREATE TABLE” statement, which was not supported on your importing MySQL server. This is now detected + handled.

David

Thanks David

I still encountered a problem with the new plugin, but only 1 problem as apposed to the 31 problems that I had yesterday!! I have emailed you a copy of the error, and look forward to hearing back from you.

Regards
Rob

Hi Rob,

Thank you – that’s a slightly different, but related, problem. I’ve emailed you a new version – please let me know how you get on with it.

David

Hi David

Thanks – I have sent you another email. Getting better, but still having a problem!

Regards
Rob

Hi David

Sent you another email this morning – still having issues – this time, with permalinks. I am pulling my hair out!

Regards
Rob

HI David

I think I may have found the problem. Something to do with mod-rewrite on my server. Trying to turn it on now, and will try again!

Regards
Rob

Hi Rob,

Do let me know if you find out the cause, and the resolution, etc… even if it wasn’t a UD issue, it helps everyone (on our side, we get less support calls!) if we can detect + advise the user of what’s up and what to do. If you need me to log in, then please send details to [email protected].

Best wishes,
David

Hi David

I have fixed the problem with the permalinks. I had to enable mod_rewrite on my server which proved quite problematic, but I got there eventually!

So, everything is working now, with the exception of the images, and I have sent you a separate email about that.

Kind regards
Rob

I found these articles useful in resolving my mod_rewrite issue :

https://xmodulo.com/2013/01/how-to-enable-mod_rewrite-in-apache2-on-debian-ubuntu.html

https://www.lavluda.com/2007/07/15/how-to-enable-mod_rewrite-in-apache22-debian/

Hi Rob,

Glad you got it all fixed!

David