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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to