All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Update sequences (optional) - When migrating content, sometimes sites will find that database sequences will be outdated or incorrect. This can result in "duplicate key" errors during the database migration to the latest version. To avoid this, before you export your data, run this older copy of the "update-sequences" command on your database. This should ensure your database sequences are updated before you dump your data.
Code Block |
---|
# If upgrading from DSpace 6.4, run this on the old server ./dspace database update-sequences # If upgrading from any other prior releaseor below, run this on your old database psql -U [database-user] -f [dspace]/etc/postgres/update-sequences.sql [database-name] # e.g. psql -U dspace -f [dspace]/etc/postgres/update-sequences.sql dspace |
The database data - Make sure to export the database data from your old DSpace site using a tool like "pg_dump" (for PostgresSQL). If you use "pg_dump", you'll end up with a large SQL file which contains all the data from your old database.
Code Block |
---|
# Example of using pg_dump to export a database to an output file pg_dump -U [db_username] [db_name] > [output_file.sql] |
...