Yes, I repeated everything from the beginning and all worked fine.
Best regards
Evgeni
On Tuesday, February 6, 2018 at 11:59:17 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> Yes, that section of the documentation is actually asking you to run the
> v5.6 "update-sequences.sql" against your
Hi Evgeni,
Yes, that section of the documentation is actually asking you to run the
v5.6 "update-sequences.sql" against your 5.6-compatible database before
upgrading it. It's not required, but sometimes if your database sequences
get out of "sync", then the database upgrade could fail.
Thank you Tim,
I followed the "Upgrade steps":
"In some scenarios, if your database's "sequences" are outdated,
inconsistent or incorrect, a
database migration error may occur (in your DSpace logs). In order to AVOID
this scenario, you
may wish to manually run the "update-sequences.sql" script
Hi Evgeni,
It sounds to me like your DSpace 6.2 upgrade didn't fully succeed *OR* you
haven't yet run all the database migrations. You might want to check your
DSpace logs (dspace.log) and/or the output of "[dspace]/bin/dspace database
status". If migrations are listed as PENDING, that means
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)
