Hello Tao Zhao, The important error seems to be this one:
Caused by: org.flywaydb.core.api.FlywayException: Validate failed: Detected applied migration not resolved locally: 5.0.2014.11.04 That error is noting that you previously (likely when you were running DSpace 5) ran a migration that was named "5.0.2014.11.04", but that same migration cannot be found any longer. The reason for this is that specific "5.0.2014.11.04" migration is an optional one, which is only run when XMLWorkflows are enabled in DSpace: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/storage/rdbms/xmlworkflow/V5_0_2014_11_04__Enable_XMLWorkflow_Migration.java If you *re-enable* XMLWorkflows in your DSpace 6.1 site, this error should go away. See Step #8 Part "d" in the Upgrade instructions at: https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace#UpgradingDSpace-UpgradeSteps Good luck, Tim On Tue, Sep 26, 2017 at 12:25 PM Tao Zhao <[email protected]> wrote: > I saw exactly the same error and could not fix it by running database > repair. > > On Friday, September 22, 2017 at 3:53:13 PM UTC-5, Tao Zhao wrote: >> >> java.sql.SQLException: Flyway migration error occurred >> at >> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:666) >> at >> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:574) >> at >> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:550) >> at org.dspace.core.Context.<clinit>(Context.java:103) >> at >> org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDSpaceWebapp.java:74) >> at >> org.dspace.app.util.DSpaceWebappListener.contextInitialized(DSpaceWebappListener.java:31) >> at >> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5118) >> at >> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5634) >> at >> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) >> "../log/dspace.log.2017-09-22" 2409L, 329890C >> >> This is becuase some tables are missing some columns, e.g. >> >> 2017-09-22 15:17:44,028 FATAL org.dspace.core.Context @ Cannot obtain the >> bean which provides a database connection. Check previous entries in the >> dspace.log to find why the db failed to initialize. The schema validator >> returned: Missing column: uuid in public.bitstream >> >> The similar error also happened to table doi, which is missing column >> dspace_object. >> >> >> Have you ever seen this error during upgrading and how did you fix it? >> >> Thanks. >> >> -- > 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 post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
