Hi Emmanuel,
Based on both errors, it sounds like some of your database
sequences need to be updated (that's usually the cause of a
"duplicate key" error).
Sometimes the underlying sequences that DSpace uses to create new content in the database can end up needing "re-syncing". This doesn't happen frequently though, but can occur especially after restoring data from a backup or restoring content via AIPs (or some other rare scenarios).
In any case, it should be easily fixable by simply running the
provided "[dspace]/etc/[db-type]/update-sequences.sql" script on
your database.
For example, if you are using PostgreSQL, you'd run something like
this:
psql -U [database-user] -f
[dspace]/etc/postgres/update-sequences.sql [database-name]
If your DSpace [database-user] and [database-name] are both named
"dspace" (which is often the case), then run this:
psql -U dspace -f [dspace]/etc/postgres/update-sequences.sql
dspace
This "update-sequences.sql" script is not harmful, and can be run
while Tomcat is still running.
- Tim
--
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...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
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