Documentation Page
https://docs.datadoghq.com/database_monitoring/setup_oracle/rac/
File: content/en/database_monitoring/setup_oracle/rac.md
Issue Description
The Oracle RAC setup instructions reference both datadog and c##datadog usernames without explaining when each applies. Customers setting up DBM on Oracle RAC hit a confusing inconsistency: the SQL to create the user shows datadog, but the example YAML uses c##datadog as the username value. This mismatch causes setup failures that look like permission errors.
Add an explicit callout explaining the distinction:
- CDB (container database) environments: Oracle requires a common user prefix — create the user as
c##datadog and use c##datadog in the YAML username field
- Non-CDB environments: use
datadog for both
- The
username value in conf.yaml must exactly match the username used in CREATE USER
Evidence: ZD #2486817, #2402341
Documentation Page
https://docs.datadoghq.com/database_monitoring/setup_oracle/rac/
File:
content/en/database_monitoring/setup_oracle/rac.mdIssue Description
The Oracle RAC setup instructions reference both
datadogandc##datadogusernames without explaining when each applies. Customers setting up DBM on Oracle RAC hit a confusing inconsistency: the SQL to create the user showsdatadog, but the example YAML usesc##datadogas the username value. This mismatch causes setup failures that look like permission errors.Add an explicit callout explaining the distinction:
c##datadogand usec##datadogin the YAMLusernamefielddatadogfor bothusernamevalue inconf.yamlmust exactly match the username used inCREATE USEREvidence: ZD #2486817, #2402341