Judging from the stacktrace, my guess is that your DB schema version
doesn't correspond to your DSpace version, for some unknown reason.
There was a significant change to several DB tables in DSpace 5 where many
entity attributes (including eperson last name) moved from the entity table
to the metadatavalue table, where they are referenced by resource_id (e.g.
eperson_id) and resource_type_id (e.g. 7 for eperson). That's how you can
tell a pre-DSpace 5 database from a DSpace 5 database. Please, check that
the schema corresponds to your DSpace version.
Assuming you're running DSpace 5 on a DSpace 4 database, DSpace 5 will
attempt to upgrade the schema automatically to DSpace 5 (this is a new
feature in DSpace 5). It will also print information about all successful
and unsuccessful migrations in the log, so check that. It will also create
the schema_version table which contains this information.
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
