We are trying to upgrade our system from 6 to 7, we are following all the steps.
We get this message on DB migration: Migration V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql failed When we attempt to update the DB, if fails right there, because it is (?) trying to create a field WHICH APPARENTLY DOES NOT EXIST in 6.x or 7.x from a previous field THAT NEVER EXISTED ON OUR 6.x install. This script, which is part of the Flyway DB upgrade auto process org/dspace/storage/rdbms/sqlmigration/postgres/V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql Contents are: DROP INDEX IF EXISTS metadatavalue_resource_type_id_idx; CREATE INDEX metadatavalue_resource_type_id_idx ON metadatavalue (resource_type_id); However, WE started with V 6.0. So, (1) that column did not exist in the 6.0 schema. (2) Furthermore, the field it is trying to create USING the value from that 5.7 field, also DOES NOT EXIST in the schema for 6.xx OR 7.xx. So, the migration script seems to be trying to alter the metadatavalue table using a column which doesn't exist to create a column that doesn't apparently exist in anyone's backend. Can anyone who either knows migrations very well, or the Dspace backend care to comment or assist? This is so super frustrating and confusing. What are we missing? Thanks so much Steven Turner -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/6fe36006-b4c3-4643-bc57-60b7bad1afb5n%40googlegroups.com.
