Aborted upgrade due to DB version
-
We were upgrading using the link on the main administration page. Unfortunately, no backup was made. We were using an older version of MySQL4 which, after a considerable portion of the upgrade was complete, was detected by the installer. We now have a half-baked installation. We have used our provider’s utilities to convert the database to MySQL5. There seem to be multiple databases and the names are different. Before we had “wp”. Now we have “fpcknox_blog”, “fpcknox_main”, and “fpcknox_surebuilder”. The last file seems to be empty.
I have the code to change the parameters in the wp-config.php file for the DB_NAME and DB_HOST (‘localhost:/tmp/mysql5.sock’ to point to the MySQL5 services). The “fpcknox” portion of the filenames is our domain name that the conversion routine probably added. I did not do the conversion so I am not certain where the other portion of the name came from. My puzzlement is why there are now three. If I had to make a wild guess I would use “fpcknox_main”. That database has 16 tables.
Any insight on how to proceed from here would be appreciated. Specifically, which filename to use and what, if anything, is needed to complete the update.
Thanks!
- The topic ‘Aborted upgrade due to DB version’ is closed to new replies.