We’re currently using Nexus Repository Manager OSS version 3.48.0-01 with OrientDB. We’re following this guide to migrate to H2:
Upgrading to H2 database - #4 by judaly
However, we’re unable to get our existing data to appear in the Nexus repo after the migration. Could you please advise if there are any extra steps or known issues with this process?
Thanks for your help!
Hello,
I did the same thing last year. I also encountered a problem, but I’m not sure exactly how it behaved.
I can only tell you what helped me. I had to go into the container and disable the entrypoint or cmd to disable the database from starting when the container started.
I mounted this script into my container and then I ran this script to reset all auto-increment counters:
However, please do this at your own risk. Since you didn’t post any error messages, it may not be your problem at all.
This script helped me, and I am now using Nexus on H2.
Good luck!
After the migration, some tasks run to rebuild the browse and search indexes. Have you ensured these have ran to completion? If not you may need to re-run them manually if you believe they may have been interrupted by a restart.
We’re running Nexus OSS 3.48.0-01 directly on an Ubuntu machine, not in a container, so we can’t use the container-specific workaround. But we’ll look into the script you mentioned to reset the auto-increment counters—it might help.
So far, we haven’t seen any errors; it’s just that the existing data doesn’t appear after migration. If we do find any errors, we’ll share them.
Appreciate your help!
Yes, we have followed all the steps outlined in the official Nexus documentation for the migration from OrientDB to H2, including the post-migration tasks. Both the repository browse and repository search index rebuilds were executed as part of the process and have completed successfully. We’ve also verified that these steps were not interrupted and do not require a manual re-run