Must-share information (formatted with Markdown ): which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) SonarQube 7.3 what are you trying to achieve Upgrade successfully to 7.3v. what have you tried so far to achieve this I tried to upgrade the SonarQube instance…

I would suggest first reviewing existing ‘unicity constraint’ errors reported here, couple of discussions on this topic. For example: [image] Upgrade of SonarQube from version 6.3 to 6.7.5 fails at step #1641 SonarQube Hello, Unicity constraint violation during a DB migra…

Hi Nicholas, Once 7.3 version is brought up,it is making connection to the DB & even after terminating the connections ,it is getting respawn.Please suggest what can be done to not to make connection with db before db migration… Thanks, Nagashree.B

Am not entirely clear on what concrete error/issue you’re hitting here. I would suggest reviewing the various SonarQube logs (see troubleshooting documentation ), looking at existing topics for similar problems, and then describing your issue more in details if needed (with corresponding logs).

Hello, I have the same problem, have you solved yours? I found on the internet: https://stackoverflow.com/questions/48666926/sonarqube-update-database-for-version-7-fails Is this a viable solution? Thank you

Hi KevinL, we have received following as output for the query to our Oracle DB: SQL> SELECT p.uuid, pm.metric_id, COUNT(1) FROM project_measures pm INNER JOIN projects p on p.uuid = pm.component_uuid INNER JOIN snapshots s on s.uuid = pm.analysis_uuid WHERE s.islast = TRUE and pm.person_id is nul…

I replaced “true” with “0”. I removed the index, and the migration worked. But I do not know the future impacts of the removal of this unique index …

Hi Nicholas, Please add Alex & Ann for the discussion & let me know if we do the action suggested by KevinL works or not & what may be the side effects for the same… Thanks, nagashree

We solved our problem, we were able to remove duplicates. select m.id, m.name, m.description, CASE WHEN d.metric_id IS NULL THEN 'ok' ELSE 'KO' END from metrics m left outer join ( select distinct a.metric_id from …

Hi Kevin, Thank you…But are these sonarsource corrections for the issue ? or do we still need to check with them on this solution? Thanks, Nagashree.B

SonarQube upgrade to 7.3 version from 6.7.5v

SonarQube Server / Community Build

NicoB (Nicolas Bontoux) October 11, 2018, 9:28pm 2

I would suggest first reviewing existing ‘unicity constraint’ errors reported here, couple of discussions on this topic. For example:

Topic		Replies	Views
Upgrade from 6.7.3 to 7.9 (LTS) -> Fail to execute CREATE UNIQUE INDEX live_measures_component SonarQube Server / Community Build sonarqube , database , oracle , migration	6	3433	November 14, 2019
SonarQube 7.3 database upgrade failed on #2114 'Add unique indexes on table users' SonarQube Server / Community Build	1	1641	September 16, 2018
MySQL5 upgrade for SonarQube V7.2.1 SonarQube Server / Community Build	18	461	August 5, 2024
Upgrade to 7.7 #2506 'Migrate quality gate conditions using warning, period and no more supported operations': failure SonarQube Server / Community Build sonarqube	3	1252	March 27, 2019
DB migration issue - During sonar upgrade from 6.7-RC1 to 7.9.6 SonarQube Server / Community Build sonarqube	7	596	August 5, 2021

SonarQube upgrade to 7.3 version from 6.7.5v

Related topics