Database upgrade fail 1.4 to 1.6

[goatherder]

I am upgrading a 1.4.1.0 store.

I am getting stuck doing auto upgrade when it goes to upgrade database it says it fails.

I did a test run of this last November and it worked fine. I can rollback without issue so that is good.

 

I raised up my PHP limits for Memory and other things but that didn't help.

 

I realized last fall when did test upgrade I did upgrade the database to MySQL 5.5 from 5.0.

So I tried upgrading database to 5.5 by creating new database and importing backup. But when I go into Database settings in 1.4 and change the settings it says Fatal Error. I restore the previous settings.inc.php to get it running again.

 

So then I tried by replacing the settings.inc.php file directly and get the same problem.

 

I know it is some what linked to the database because one time I put the wrong address in for database and it said it couldn't link to database.

 

So am stumped at what I should try next to get this darn store upgraded. Perhaps the rollback after failed upgrade has changed something with database handling?

Edited July 17, 2016 by goatherder (see edit history)

[goatherder]

I just changed my permission to 755 from 644 on the settings file and now it gives Bad Sub-domain SQL Query error. That is all you see on screen.

 

UPDATE

I am maybe seeing issue with the database address change and sql error now. The database backup from before upgrade doesn't contain all the PS_ tables that are in current database for some reason. Think the rollback during upgrade changed the database structure maybe?

 

UPDATE

Nope, any backup I create is missing 30 tables when I create new database from backup.

 

UPDATE

Talking to myself, but maybe help someone else in future. Think the whole problem is Database size. It is 148mb due to that known issue with ps_connections never emptying. Going to do another backup using export option, not using an automated tool for the database. Before I try to Truncate the ps_connections table and some other tables.

Edited July 17, 2016 by goatherder (see edit history)

[goatherder]

Another day and progress. Truncated/cleared the the PS_Connections, PS_connections_source, PS_Guests entries in the database and now down to 55mb. This whole experience makes me think the makers of Prestashop should have made a tool in the upgrade process to give the option to clear some of these if they are very large. Looking at previous posts it is obvious this database size bloating issue is not new. It has been around for years. With my host its clear the shared server can't handle the size of the database. Others have and will probably run into the same thing.

 

Now to try the upgrade again for the store.

[goatherder]

Ok, final update.

 

Think I have most things working now.

 

Had some problems at first. Kept getting an error about TWENGA not loading or missing after switching to the new default theme for 1.6. But in Advanced Parameters a quick recompile of templates seemed to fix it.

 

Now if I could just find a way to do shipping estimates like I know I turned on when I did test upgrade last fall.