Importing old DB to new only brings in 29 tables

[rstevenson]

Hi,

Old site is v1.3.7, new one is 1.3.9h

New site is a completely fresh install with new template and so on. The complication is that the new site, for many reasons, is being created on a new host.

I went into the cpanel of the old site, into phpMyadmin and did a database export using the settings suggested in the Tutorials/FAQ. No warnings were received and all seemed fine. Going into the new site's cpanel and phpMyadmin and importing also gave no errors and all seemed well. But the old DB had 93 tables (as usual) and the newly imported one gets only 29 tables -- the first 29 in alpha order.

Obviously the new site is not working now. (The old one is still live, and the domain names still point to it, so no panic.)

Any ideas what's wrong?

Rob

[rstevenson]

Solved, almost. I exported into 4 separate files, and then imported them. Doing this indicated a problem existed in the email_archive table, since the import of that part stopped at that point. I left the data imported in that table and proceeded to import all the other tables and I now have a database with 93 tabes in it. Phew!

But... what do I do about the email_archive data? Presumably it was corrupted and is even more so now since it's incomplete. Do I delete all the records in it?

Rob

[eentje]

in your old database select the email archive records then export them to a textfile.

This textfile can be uploaded to your new db.

It might be if you used the email functioon of zen cart a lot that the table is to long to import in 1 piece.

So you might have to cut it in half by hand.

[rstevenson]

Thanks for the suggestion. I may do that just to have a look. But I don't think size of file is the issue. When I broke it up, the second part started with the email_archive table and went on from there, but the export stopped at the same place in that table even though there was no data at all ahead of that table. I think there must be some corrupted data at the point at which the export stops. I may find it when I look at the txt file, as you suggested.

But the good news is the site owner doesn't care about the email archive. So I can just skip it and leave an empty table.

Rob

[eentje]

If the owner doesn't care about the archive... then you shouldn't either... :)

Or just download the sql file from the old db, zip it up for archive purpose and give it to the owner... just in case.

[rstevenson]

Good idea.

Rob