I updated a small test repository from 5.6 to 6.2. Quite smoothly and all
works in the end, but two questions appeared:
1. Running update-sequences.sql there was an error message:
psql -U dspace -f D:\DSPACE.5.6.n\DSPACE\etc\postgres\update-sequences.sql
dspace56n
...
setval
--------
(1 row)
psql:D:/DSPACE.5.6.n/DSPACE/etc/postgres/update-sequences.sql:63: ERROR:
relation "handle_id_seq" does not exist
LINE 1: SELECT setval('handle_id_seq', max(handle_id)) FROM handle;
^
setval
--------
42
(1 row)
Is this an error in the script or an error in the database? Is not
update-sequences.sql supposed to fix errors, not to report errors?
2. In the "Upgrade Steps" there is "The database migration should also
trigger your metadata/file registries to be automatically updated (based on
the config files in [dspace]/config/registries/). However, if this update
was NOT triggered, you can also manually run these registry updates (they
will not harm existing registry contents)."
How can I know was the update of "metadata/file registries" triggered or
not? What does registry-loader do? What if I run
[dspace]/bin/dspace registry-loader -metadata
[dspace]/config/registries/dcterms-types.xml
without knowing was the update already triggered or not?
Best regards
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
