hello dudes
anybody can provide a detailed help on upgrading from 0.8.5 to 1.0
the helps on following links does not help much:
http://doc.mimec.org/webissues/server/upgrade_server.html
http://doc.mimec.org/webissues/1.0/en/webissues.admin.updating.html
the directories structure seems to be totally different from v0.8.5 to v1.0
thanks
- Log in to post comments
Same problem here, when I try to upgrade the database I get an error message that the old database is not compatible with the new one.
Why don't you just read the manual?
"Although a direct upgrade from version 0.8.5 of the server is not possible, existing data can be imported from version 0.8.5 of the WebIssues server when installing a new version of the system. More information can be found in the section called “Installation”."
Regards,
Michał
thanks Michal that worked but with some errors:
[Unexpected Error
An unexpected error occured while processing the request.
Reason: One of the dependent objects no longer exists.]
However all tables is copied to new table with the prefix "wi1_" except "attr_values", "comments" and "changes".
using phpmyadmin, I managed to manually delete "wi1_attr_values" and "wi1_comments" and recreate them with "wi1_" prefix.
but I couldn't delete "changes" table as it returns error:
#1217 - Cannot delete or update a parent row: a foreign key constraint fails
nor i can copy the content of old "changes" to new "wi1_changes" as it returns error:
#1136 - Column count doesn't match value count at row 1
I am not so familiar with Mysql. anybody can kindly help me?
"(...) Reason: One of the dependent objects no longer exists.]"
I have the same error. I suspect this is because I manually removed some entries in the past :-).
1. Is there any logfile containing more detailed information describing what element caused the failure? I could try to fix the problem manually, if I knew where it is.
2. What is the simplest way to restart the installation process, if the tables already exist? Should I just drop tables with given prefix in SQL?
Yes, the problem is related to some data integrity error.
You can enable debug mode logging, which is described in the Wiki.
You can simply remove the "new" tables and restart the installation process.
Regards,
Michał
this is my output when debugging enabled. I cannot get anything out of it. any friend can save me out this mess?
Looks like there's some attribute values for which no issue exists. Try the following query on the source data to find those values:
Regards,
Michał
thanks, thanks, thanks
that was exactly the problem. I dropped the junk values and all the migration process passed successfully.
thanks again.