Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 3.37.0
-
Fix Version/s: 3.38.0
-
Component/s: Database Migrator, Database PostgreSQL
-
Epic Link:
-
Sprint:NXRM Sentinels Sprint 28
-
Notability:2
-
InvestmentLayer:support-escalated
Description
SYMPTOM:
As per https://help.sonatype.com/repomanager3/installation-and-upgrades/migrating-to-a-new-database, the migrator jar accept the schema name with "¤tSchema=nexus", but after doing this and re-starting NXRM 3.37, it fails with below:
2021-12-01 18:58:06,235+1000 ERROR [FelixStartLevel] *SYSTEM org.flywaydb.core.internal.command.DbMigrate - Migration of schema "nexus" to version "1.3 - JobDescriptionMigrationStep_1_3" failed! Changes successfully rolled back. 2021-12-01 18:58:06,238+1000 ERROR [FelixStartLevel] *SYSTEM org.sonatype.nexus.upgrade.datastore.internal.UpgradeServiceImpl - Failed transition: NEW -> STARTED org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException: SQL State : 42P01 Error Code : 0 Message : ERROR: relation "public.qrtz_job_details" does not exist
REPRODUCE STEPS:
- Install a new NXRM 3.37 with OrientDB
- Prepare PostgreSQL with a new database (eg: nxrm), a new schema (eg: nexus), and a DB user for nexus
- Run the migrator with "¤tSchema=nexus", and confirm it completes without any error
- Prepaire nexus-store.properties file, which includes the line "schema=nexus"
- Start Nexus normally
EXPECTED RESULT:
It should start successfully as this works with previous versions.
POTENTIAL CAUSE:
In the org.sonatype.nexus.quartz.internal.upgrades.JobDescriptionMigrationStep_1_3, we use the following:
private static final String STATEMENT = "ALTER TABLE public.%s ALTER COLUMN description TYPE text";
Attachments
Issue Links
- is caused by
-
NEXUS-28921 Browse page is empty after migrating to the New DB because Rebuild repository browse tree task fails to be stored due to long name
-
- Closed
-