# SonarQube upgrade to 7.3 version from 6.7.5v

**URL:** <https://community.sonarsource.com/t/sonarqube-upgrade-to-7-3-version-from-6-7-5v/3283>\
**Category:** SonarQube Server / Community Build\
**Tags:** database, sonarqube\
**Created:** [October 11, 2018, 7:37pm UTC](https://community.sonarsource.com/t/sonarqube-upgrade-to-7-3-version-from-6-7-5v/3283 "2018-10-11T19:37:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![NicoB](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/nicob/32/3_2.png) [@NicoB](https://community.sonarsource.com/u/NicoB)\
**Post date:** [October 11, 2018, 9:28pm UTC](https://community.sonarsource.com/t/sonarqube-upgrade-to-7-3-version-from-6-7-5v/3283/2 "2018-10-11T21:28:39Z")

</div>

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

> [@Upgrade of SonarQube from version 6.3 to 6.7.5 fails at step #1641](https://community.sonarsource.com/t/upgrade-of-sonarqube-from-version-6-3-to-6-7-5-fails-at-step-1641/2669/3):
>
> Hello, Unicity constraint violation during a DB migration does indicate a potential problem with the dataset itself. Either during this upgrade an instance was connected to the database and changing the dataset, or you are working with a dump done in hot backup mode. Anyway, you need to check that no instance is connected to the db while performing the migration or to get a dump done in cold backup mode. Greetings, Alex.

---

_[View the full topic](https://community.sonarsource.com/t/sonarqube-upgrade-to-7-3-version-from-6-7-5v/3283)._