Trouble updating database

[NWCE]

Hello again,

I have tried deleting my new v.1.5.4 database in MySQL and then creating a new one and tried Importing in the old v.1.5.3 database into this v.1.5.4 one using PHPMyAdmin Import. After it completes, I still only get 160 tables and when looking in MySQL Databases in Cpanel to look at the size....my current v.1.5.3 is 232 Mb and my v.1.5.4 is only 200Mb.

Still stumped as to why it is not importing the entire database.

Does anyone have any other suggestions?

Thanks in advance,

Jeff

[mc12345678]

Hello again,

I have tried deleting my new v.1.5.4 database in MySQL and then creating a new one and tried Importing in the old v.1.5.3 database into this v.1.5.4 one using PHPMyAdmin Import. After it completes, I still only get 160 tables and when looking in MySQL Databases in Cpanel to look at the size....my current v.1.5.3 is 232 Mb and my v.1.5.4 is only 200Mb.

Still stumped as to why it is not importing the entire database.

Does anyone have any other suggestions?

Thanks in advance,

Jeff

If you export your "new"database, is the size the same as the export of the old database? Might not be the import process, but instead the export process that is changing things.

[NWCE]

Hi mc12345678,

Thanks for your reply and suggestion. The export process that I am using is from a Zen Cart plugin Backup My SQL, and I have done a couple today, to insure it wasn't being corrupted during the process.

The biggest thing I see in my "new" database is the tables only go down to "Paypal" and then no other tables are importing after that, even though when I look at my old database they are all there. I have tried doing a check database in Cpanel, and all items say OK. Not sure why the remaining tables are not being imported in.

Any ideas?

Thanks again,

Jeff

[mc12345678]

Hi mc12345678,

Thanks for your reply and suggestion. The export process that I am using is from a Zen Cart plugin Backup My SQL, and I have done a couple today, to insure it wasn't being corrupted during the process.

The biggest thing I see in my "new" database is the tables only go down to "Paypal" and then no other tables are importing after that, even though when I look at my old database they are all there. I have tried doing a check database in Cpanel, and all items say OK. Not sure why the remaining tables are not being imported in.

Any ideas?

Thanks again,

Jeff

So, with that in mind, there are a few things possible here. The tables that have not been transferred over, do they start with the same prefix as the tables that are transferred?

160 tables is a great number of tables more than a default install that even has several other modifications associated...

The default install has just under 100, so something has added at least 60 tables to your database.

So in answer to teh question of any ideas, well thinking that the backup program is doing what it is expected to do which would be to backup the database information applicable to your store and that the remaining tables are not so associated because they do not fit the parameters... Just my thought on the matter when using this method of backup and without further information.

The other part of it, and if I remember correctly is associated with your issue is that perhaps there is a timeout occurring that is killing the process too early. Perhaps could copy the backup file, edit it to remove the first set(s) of tables and try to upload just the remaining tables.

[NWCE]

Thanks again for your reply mc12345678.

Upon closer examination my tables in my database (current one as well) basically has 3 sets of the same tables. The first set has no prefix to it, and the identical second set of tables has a prefix, and the third set has a different prefix (the one that I associate with my database when filling in the information during zc_install). All of these three sets make up my complete database of 250 tables. Our store is 9 years old, but I have only taken over the upgrading process, etc. over the last 4 years and have always just copied current databases into new when upgrading.

I have checked and there is information in all of these but it appears that the last set has the up to date information. (i.e. when I look at the customers table, it contains the correct number of entries as compared to my Zen admin panel results, as well as all 2015 data.) The other 2 tables look to only contain some info and dates back to 2007 and some in 2012. I have only checked a couple of tables information to find this out, not all of them.

So, this is a whole new kettle of fish! Can I simply delete the extra 2 sets of tables? Is it best to delete them from MyPHPAdmin? I would do a database backup, put the site down for maintenance, delete the 2 sets of tables that seem to be not necessary, and then see if my site runs as it should. Is this the best idea?

Thanks again for your help,
Jeff

[NWCE]

All of these three sets make up my complete database of 250 tables.

Sorry to edit the last post...there is a second page to my current database when displaying in PHPMyAdmin with an additional 59 tables so a total of 309. My "new" database still only has the one page with 160.

Jeff

[mc12345678]

So, yes before making database changes, a trusted backup should be made...

Next,if you have duplicates of table names with the difference only being the prefix (and of course content) then I would suggest deleting the duplicates. Of course need to know which table prefix is your live table prefix.. (DB_PREFIX in includes/configure.php)

So if the DB_PREFIX is zen_ for your active store, then configuration, zc_configuration, longlist_configuration could all be removed and not affect your current store. Would also suggest looking at the structure of the table(s), to ensure that even though there is a "different" prefix that the table doesn't represent something else that is instead important.

It's no wonder that the database size is so large, there are something like 4 different stores in it.

Generally speaking though, shouldn't have to place the store in maintenance mode...if doing things right, then the rest of the world wouldn't even know that there was anything going on in the background.

[NWCE]

Thanks for your help with this mc12345678. I will try this tomorrow and will post back once done to let you know and hopefully others if they are having the same issue.

Thanks,

Jeff

[lhungil]

Most hosting providers place a limit on how long a PHP script (such as phpMyAdmin) can run before the script is foribly terminated. When this happens, data will be only patially imported. By defualt phpMyAdmin when importing has an option to "skip" portions of the import when it detects the amount of time is reaching this limit imposed by the hosting provider.

The usual fix is to use an alternative tool to import the data (commandline via SSH; Backup MySQL module for Zen Cart uses exec w/ commandline to restore)... Or break the original export into smaller amounts (via phpMyAdmin or another tool), and import each smaller amount one at a time.

So yes, limiting your export to just the currently in use tables should help!

[NWCE]

Hi lhungil,

Thanks for this info on the limits. I appreciate it! I did not know this, and will try your suggestions. Do you know how to import the database into the new v.1.5.4 using the Zen Cart Backup MySQL tool as I have it installed and would love to be able to use it to import my database as I then for sure won't run into the timeouts.

Thanks again,
Jeff