Migrate OrientDB to H2 stuck on "userToken"

Sonatype Nexus Repository
1

Hello I have a problem migrating the OrientDB to H2 on our Nexus 3.70.3-01 OSS instance.
As an important info: Some years ago we were running the instance on Nexus PRO, but switched back to OSS.

When running the db-migrator, I get the following error message:

[nexus@apwedevlnxdo18 component]$ java -jar ../../db-migration/nexus-db-migrator-3.70.3-01.jar --migration_type=h2
...
16:03:01 [main] ERROR o.s.batch.core.step.AbstractStep - Encountered an error executing step checkModelVersionsStep in job migrationFromOrientNoExportJSONJob
com.sonatype.nexus.db.migrator.exception.WrongSchemaVersionException: Occurring schema versions that are not supported:
Upgrade ModelVersions{config='1.10', security='1.4', component='1.16', healthCheck='1.1', userToken='1.1', tags='1.1'}
Supported schema versions:
Upgrade ModelVersions{config='1.10', security='1.4', component='1.16', healthCheck='1.1', userToken='1.5', tags='1.1'}
Your OrientDB schemas are not supported by the current migrator version. Please update your Nexus Repository to the 3.70.1 version and use latest migrator version.

It looks like our OrientDB still got information regarding the “userToken” db version 1.1 - which is part of the PRO version(?).

Does anybody know on either how to get rid of the “userToken” or how to change the version to 1.5. so the migrator will continue?

Thanks in advance,
Rainer

2

I don’t recall the name of the table, but you should be able to connect to the OrientDB and set the userToken value to null.

3

I found in the config database the following entry:

orientdb {db=config}> select usertoken from upgrade_model_versions;

+----+---------+
| #   |usertoken|
+----+---------+
|0   |1.1      |
+----+---------+

1 item(s) found. Query executed ` `in` `0.003 sec(s).

I have now updated the value to “1.5”:

orientdb {db=config}> UPDATE upgrade_model_versions SET usertoken = 1.5

Updated record(s) ` `'1'` `in` `0.019000 sec(s).

Then I was able to run the migrator successfully.
I am currently testing, if the migrated Nexus instance is accepting the new H2 database.