In some cases, when you restore a large amount of content to your DSpace, the internal database counts (called "sequences") may get out of sync with the handles of the content you just restored. As a best practice, it's recommended to *always* re-run the "update-sequences.sql" script on your DSpace database after a larger scale restore. This database script can be run while the system is online, and is found in the following locations for PostgreSQL and Oracle, respectively:
{{\[dspace\]/etc/postgres/update-sequences.sql}}
{{\[dspace\]/etc/postgresoracle/update-sequences.sql}} |