Hi, Have you tried reindexing everything? Assuming the import worked properly (no obvious errors in logs), then it's possible the content isn't showing because the reindex process either hasn't been triggered or somehow failed.
So, I'd recommend trying: "[dspace]/bin/dspace index-discovery -b" while Tomcat/Solr are running. This may take a while for a large amount of content, but you should be able to watch its progress via the dspace.log. If that doesn't work, then I'd recommend checking that your database *has content* in the "community", "collection" and "item" tables. If there's nothing in there, then the problem was with the import process. The error you received from the "update-sequences" script almost sounds like it cannot see any content in the "handle" table, which again may imply the import didn't work as expected. Tim On Monday, May 20, 2024 at 8:44:09 AM UTC-5 dba...@gmail.com wrote: > I have a DSpace 5.10 instance that I have exported the entire site from > using AIP. > > I have a freshly installed DSpace 7.6.1 instance that I have imported all > content into ( > [dspace]/bin/dspace packager -r -a -f -t AIP -e <eperson> -i > <site-handle-prefix>/0 -o skipIfParentMissing=true > /full/path/to/your/site-aip.zip). > The import was successful and imported over 200 GB of data. > > However, when I log into the new instance, I do not see any communities or > collections. I performed a server reboot to make sure all services were > restarted OK, but still no communities/collections. I also tried to run > 'dspace database update-sequences', but I get the following error: > > Running org/dspace/storage/rdbms/sqlmigration/postgres/update-sequences.sql > Caught exception: > org.postgresql.util.PSQLException: ERROR: setval: value 0 is out of bounds > for sequence "handle_seq" (1..9223372036854775807) > at > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713) > at > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2401) > at > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:368) > at > org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:498) > at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:415) > at > org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:335) > at > org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:321) > at > org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:297) > at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:292) > at > org.apache.commons.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:193) > at > org.apache.commons.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:193) > at > org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:405) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:568) > at > org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:283) > at > org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:134) > at > org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:99) > > I'm not sure if update-sequences.sql will fix my issue anyway. Any other > ideas? Thanks. > -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/578ab56c-f013-4d14-92ae-ce5a1c97308fn%40googlegroups.com.
