Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When having two sonarqube schemas on the same Oracle instance, especially if they are in 2 different versions, SonarQube can get confused and picks the first it finds. In that case, there are two known workarounds:
1. Remove the DBA rights to the sonarqube users in Oracle
2. Use Set the sonar.hibernatejdbc.default_schema property in sonar.properties to set the schema. In that case, -Dsonar.hibernate.default_schema should be used as well during project analysis.right schema (same thing on the analyzer side: sonar-runner.properties or pom.xml or ...)

Cannot connect to MySQL database

...