I'm attaching the output of our ./dspace database info below, but it shows that prior to our upgrade attempt the last successful migration was 6.1.2017.01.03 in 2017, and 4.9.2015.10.26, 5.0.2014.11.04, 5.7.2017.05.05, and 6.0.2015.09.01 had been Ignored.
I have a theory, and if anybody can tell me if it seems to be on the right track (or way off), what else we should be looking at, or anything else I would be very grateful. the 5.7.2017.05.05 migration that is failing is to Add Policies for BasicWorkflow, and one of the migrations that had been skipped (but ran successful as an Out of Order migration as we tried to update) was 5.0.2014.11.04, Enable XMLWorkflow Migration. Combined with the error returned about types not matching, it seems possible we did not run the 5.0.2014.11.04 migration and have since ingested a lot of data into our database with a field of type int when it should have been changed to type uuid. Now, since the migrations have been ignored for a mighty long time, it's causing this trouble when trying to upgrade.
If anybody has any input or suggestions, or ideas for more data or other places to look that might be helpful, we would be most appreciative.
Ed Hill
Developer and Applications Administrator
Colorado State University Libraries