Upgrade from 5.6.3 to 7.3v

Hi All,
we are using SonarQube 5.6.3 version currently.we want to upgrade it to 7.3version.Thus please let us know how to proceed in this task.

  • which versions are you using : SonarQube 5.6.3
    sonar-java-plugin-3.13.1 sonar-ldap-plugin- sonar-scm-svn-plugin-1.3
    sonar-csharp-plugin-5.0 sonar-javascript-plugin-2.11 sonar-scm-git-plugin-1.2

  • what are you trying to achieve
    would like to upgrade to 7.3v of sonarQube with all the compatible plugins.

  • what have you tried so far to achieve this
    I am new to this and still in starting phase of reading the documents available in the sonarQube site.Please let me know the order of upgrading and compatible versions of plugins and easy documentation for upgrading each time.


Hello Nagashree,

Good to hear you’re upgrading to the latest SonarQube version. The SonarQube upgrade documentation should provide you with full guidance on your upgrade journey.

Based on the plugin compatibility matrix, all your plugins have newer versions, but they are supported.

Note that since you have an LTS your migration path, you will need to first upgrade to 6.7.x LTS and then to SonarQube v7.3. i.e., migration path is 5.6.3 > 6.7.x LTS > 7.3.

Good luck upgrading and please reach out if you need further assistance.


1 Like

Hello Clint,
Thank you for your assistance on the workflow .I have few questions to be assisted with .Please help on those:

1.)Is current version 5.6.3v is an LTS ?
2.)Currently our sandbox server does not have any configuration for database except the H2 default db.,so do we need to do any additional setup here?
3.)Please may i know the Support link(for LTS,if any issue comes up during upgrade) ,which i could not find anywhere in the documentation…


Hello Clint,

I would like to know which Edition currently we have .may i know how to check on it please…



If you’re running v5.6.x then the notion of Edition does not apply to such old versions. Starting from v6.7.x you can see which Edition you’re running in the Marketplace page (admin interface). Ultimately if you have any commercial contacts with SonarSource, then you can check which Edition your license would correspond to.

To your other questions: v5.6.x was an LTS but is now end-of-life since November 2017 (date where 6.7.x LTS was released). You’re free to evaluate later versions on H2, however any production/live installation should be done with an actual supported database.

As for Support: this forum is the open community forum where anyone can discuss about SonarSource products and get help. If you’re looking for more private technical support, then you should get in touch with SonarSource directly (dedicated technical support is available in commercial editions).

We went thru this last year. After much thought and several tests of this upgrade we decided to not proceed with it and instead to “start over”. The versions are so different that the historical trends prior to the upgrade really would serve no purpose. That combined with the fact that the rules and how quality profiles are managed are very different in the 7.x series, led us to this decision. We also had a ton of old/legacy projects and with the change over to license costs being based on LOC scanned, we felt that we would be spending a bunch of money on that too.

A year later I think we made the right decision.


1 Like

Hi ,

I have contacted SonarSource .They again redirected to Community for technical questions…
Currently ,we don’t have any db usage in our Sandbox machine and administrator password is unknown.So we would like to reset the password and try to upgrade:

1.)Can we upgrade a commercial edition from 5.6.3v to 6.7.5(LTS)?currently we have only Sandbox & testing environment ,no production environment…

2.)If yes,please let me know what is the edition that i should unzip inside “$NEW_HOMESONARQUBE/extensions/plugins” ?

3.)Please let me know how to reset the admin credentials and I found a query can help on the same from documentation but what should be queried to ?is it embedded h2 db ?If yes,please let me know how to…

4.)please let me know the support link to install all newer versions of plugins compatible with 6.75v


Hi Nagashree,

First of all allow me to remind that if you used licensed plugins in v5.6.x, then these licenses cannot work with 6.7.x. Starting from 6.7.x you need to obtain a license from SonarSource corresponding to a specific Edition (Developer/Enterprise/DataCenter, Community being the free/open-source edition).

Once you’ve got a license for a specific Edition, then to answer your question 2: you can download v6.7.x Edition package here, where you’ll also find guidance if Looking to upgrade from an older version ? (see section in docs).
(note for readers: since 7.2, Editions are now packaged and distributed @ sonarqube.org/downloads/ )

It’s also worth reminding that it is not possible to upgrade a SonarQube relying on embedded H2 database (must be used for evaluation only). If your SonarQube is connected to a proper DB then you can upgrade it as documented, and then against that DB you can leverage instructions to reset admin credentials if needed.

Last but not least, for cross-checking Plugin compatibility: https://docs.sonarqube.org/display/PLUG/Plugin+Version+Matrix

Hi Nicolas,

Once you’ve got a license for a specific Edition, then to answer your question 2: you can download v6.7.x Edition package here , where you’ll also find guidance if Looking to upgrade from an older version ? (see section in docs).

I have followed the instructions as in above link ,but i am unable to connect to database.web process is showing below error…

2018.09.17 02:59:35 INFO  web[][o.sonar.db.Database] Create JDBC data source for jdbc:oracle:thin:@lndbd201.hphc.org:1531:toldev1
2018.09.17 02:59:35 ERROR web[][o.s.s.p.Platform] Web server startup failed
java.lang.IllegalStateException: Can not connect to database. Please check connectivity and settings (see the properties prefixed by 'sonar.jdbc.').
        at org.sonar.db.DefaultDatabase.checkConnection(DefaultDatabase.java:108)
        at org.sonar.db.DefaultDatabase.start(DefaultDatabase.java:75)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:110)
        at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.start(ReflectionLifecycleStrategy.java:89)
        at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.start(AbstractInjectionFactory.java:84)
        at org.picocontainer.behaviors.AbstractBehavior.start(AbstractBehavior.java:169)
        at org.picocontainer.behaviors.Stored$RealComponentLifecycle.start(Stored.java:132)
        at org.picocontainer.behaviors.Stored.start(Stored.java:110)
        at org.picocontainer.DefaultPicoContainer.potentiallyStartAdapter(DefaultPicoContainer.java:1016)
        at org.picocontainer.DefaultPicoContainer.startAdapters(DefaultPicoContainer.java:1009)
        at org.picocontainer.DefaultPicoContainer.start(DefaultPicoContainer.java:767)
        at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:134)
        at org.sonar.server.platform.platformlevel.PlatformLevel.start(PlatformLevel.java:90)
        at org.sonar.server.platform.Platform.start(Platform.java:211)
        at org.sonar.server.platform.Platform.startLevel1Container(Platform.java:170)
        at org.sonar.server.platform.Platform.init(Platform.java:86)
        at org.sonar.server.platform.web.PlatformServletContextListener.contextInitialized(PlatformServletContextListener.java:45)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4745)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5207)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1419)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1409)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01017: invalid username/password; logon denied
        at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
        at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
        at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
        at org.sonar.db.profiling.NullConnectionInterceptor.getConnection(NullConnectionInterceptor.java:31)
        at org.sonar.db.profiling.ProfiledDataSource.getConnection(ProfiledDataSource.java:323)
        at org.sonar.db.DefaultDatabase.checkConnection(DefaultDatabase.java:106)
        ... 29 common frames omitted
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)
        at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:573)
        at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:431)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
        at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:366)
        at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:752)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:366)
        at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536)
        at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
        at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
        at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
        at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
        at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
        at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
        ... 34 common frames omitted

please let me know if any plugin or file needs to be added…

as far as database credential,DBA team could connect to the schema with the credentials confiured in our sonar.conf

sonar.jdbc.url: jdbc:oracle:thin:@server.hphc.org:1531:toldev1
#sonar.jdbc.driverClassname: oracle.jdbc.OracleDriver
sonar.jdbc.dialect: oracle
sonar.jdbc.validationQuery: select 1 from dual


This latest error is quite distinct from your initial questions here, I would recommend opening a distinct topic if it remains after troubleshooting on your side.

The error itself though:

Is pretty clear from PostgreSQL stack. I would recommend checking connectivity from same machine with same credentials.

Hi Nicholas,

sure,i will open a new topic for the error but may i know what all jar files should be placed in order to get a oracle JDBC connectivity for SonarQube please…


Hi Nicholas,

I have raised another topic for the error we have got…Please let me know what are the below plugins used for & do we need to install new version of them under /data folder or not…

asm-debug-all-5.0.3.jar java-jacoco-previous-
cglib-nodep-3.1.jar java-maven-model-
commons-lang-2.6.jar java-surefire-
gson-2.6.2.jar jsr305-1.3.9.jar
guava-19.0.jar org.jacoco.core-
java-checks- picocontainer-2.14.1.jar
java-frontend- sslr-core-1.21.jar
java-jacoco- sslr-squid-bridge-2.6.1.jar

we have these plugins in our UAT instance which is still 5.6.3version .Need little explanation on the purpose of /web folder under /data folder (we have got this after unzipping the package).


Hi Team, We are currently using SOnarQube version 5.6.6 in our organization. Our plan is to migrate it to version 8.3. I got to know that our journey path should be
5.6.6 (current) > 5.6.7 > 6.7 > 7.9 > 8.3 (target)
I want to know whether we MS SQL 2017 supports all the previous versions and can we perform the upgrade using it ?


Welcome to the community!

First, no need to upgrade to 5.6.7. You’re on a point version of that LTS, so you’re good as far as that’s concerned.

Regarding MS SQL, It looks like the latest version at the time of 6.7 was 2016. And that version is still supported through SonarQube 8.3.

If you’ve already upgraded your DB to 2017 and your 5.6.6 instance of SQ is running fine, then you should be good for the upgrade. If you’re looking at concurrently upgrading both sides of the equation (DB and SonarQube) then maybe don’t upgrade the DB first…?