Hi, You are running the wrong "update-sequences.sql" script (as that "handle_id_seq" is in the v7 script, not the v4 one)... likely because you tried to copy the v4 one into your v7 codebase. That won't work, because DSpace 7 will likely use the update-sequences.sql script that is embedded in dspace-api.jar.
Instead, if you need to run the v4 update-sequences.sql manually by just doing something like this: psql -U dspace -f full/path/to/update-sequences.sql (This is assuming your DSpace database user account is named "dspace". If it isn't, then you need to change the "-U" param. For more information on psql see https://www.postgresql.org/docs/current/app-psql.html) Tim On Saturday, August 27, 2022 at 10:16:52 PM UTC-5 Night Librarian wrote: > So, since I re-started the migration/upgrade process from the beginning, I > re-downloaded the 4.x version update-sequences.sql from > https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace/etc/postgres/update-sequences.sql > > like I did in March and placed it in > /temp/DSpace-dspace-7.2/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/postgres. > > What I don't understand, is that in March, after replacing the 7.x version > by 4.x, it completed successfully: > > *$ ./dspace database update-sequences* > > Running > org/dspace/storage/rdbms/sqlmigration/postgres/update-sequences.sql > > update-sequences complete > > > Today, the terminal shows this: > > Running > org/dspace/storage/rdbms/sqlmigration/postgres/update-sequences.sql > > Caught exception: > > org.postgresql.util.PSQLException: ERROR: relation "handle_id_seq" does > not exist > > Position: 16 > > at > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565) > > > at > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297) > > > at > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322) > > at > org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481) > > at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401) > > at > org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322) > > at > org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308) > > at > org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284) > > at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279) > > at > org.apache.commons.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:194) > > > at > org.apache.commons.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:194) > > > at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:353) > > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > > > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > > at > org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:277) > > at > org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:133) > > at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98) > > It's the exact error I got in March before I downloaded the 4.x > update-sequences.sql and ran the command successfully. This time, it > doesn't work. Am I using a wrong directory to store the file? Could there > be a problem with permissions? What else am I missing? > > > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/37e6c780-62c9-4750-94ab-e251e255b8een%40googlegroups.com.
