aboutsummaryrefslogtreecommitdiffstats
path: root/server
diff options
context:
space:
mode:
authorkevin-hinz <kevin.hinz@sonarsource.com>2022-08-16 10:50:43 +0200
committersonartech <sonartech@sonarsource.com>2022-08-17 20:03:09 +0000
commit3746b376bd2fa043625f5293bfe1464b3bdbbc00 (patch)
treebdb0138f1c7362a83116363b225a15b72123bfe9 /server
parent3f16440adb8aeda11f7fcdc38c5aae15143bfbb5 (diff)
downloadsonarqube-3746b376bd2fa043625f5293bfe1464b3bdbbc00.tar.gz
sonarqube-3746b376bd2fa043625f5293bfe1464b3bdbbc00.zip
DOC-14 replace missing text
Diffstat (limited to 'server')
-rw-r--r--server/sonar-docs/src/pages/setup/install-server.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/server/sonar-docs/src/pages/setup/install-server.md b/server/sonar-docs/src/pages/setup/install-server.md
index 7906e686a38..8e5ab3f158a 100644
--- a/server/sonar-docs/src/pages/setup/install-server.md
+++ b/server/sonar-docs/src/pages/setup/install-server.md
@@ -85,7 +85,8 @@ Create an empty schema and a `sonarqube` user. Grant this `sonarqube` user permi
|If there are two SonarQube schemas on the same Oracle instance, especially if they are for two different versions, SonarQube gets confused and picks the first it finds. To avoid this issue:
|
|- Either privileges associated to the SonarQube Oracle user should be decreased
-|- Or a trigger should be defined on the Oracle side to automatically alter the SonarQube Oracle user session when establishing a new connection:
+|- Or a trigger should be defined on the Oracle side to automatically alter the SonarQube Oracle user session when establishing a new connection:
+| `ALTER SESSION SET current_schema="MY_SONARQUBE_SCHEMA"`
|
|[[warning]]
|| Oracle JDBC driver versions 12.1.0.1 and 12.1.0.2 have major bugs, and are not recommended for use with the SonarQube ([see more details](https://groups.google.com/forum/#!msg/sonarqube/Ahqt1iarqJg/u0BVRJZnBQAJ)).