Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[DBM] Oracle RAC setup page should clarify c##datadog vs datadog username requirement

Open
#35,996 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@HassData is already working on this.

Since Apr 17, 2026.

  • #36084 by @HassData — closed without merging
  • #36088 by @HassData — closed without merging

Assessment

This issue has not been assessed yet.

Description

documentation

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 page uses a generic shortcode for the "Create the Datadog user" step that shows CREATE USER datadog (non-CDB), but the YAML configuration example on the same page hardcodes username: 'c##datadog' (CDB/multitenant) with no explanation.

Oracle RAC supports both CDB and non-CDB configurations depending on the Oracle version and setup:

  • Oracle 11g RAC: always non-CDB — use datadog
  • Oracle 12c+ RAC (CDB/multitenant): use c##datadog
  • Oracle 12c+ RAC (non-CDB): use datadog

The "Create the Datadog user" section should use the same tab structure as the self-hosted Oracle setup page (Multi-tenant, Non-CDB, Oracle 11), and the YAML example should be updated to match with tabs showing the correct username for each configuration.

Dominant language
JavaScript
Stars
622
Forks
1.3k
Avg merge
2d 10h
Merged PRs (30d)
483

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataDog/documentation

All issues in DataDog/documentation

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.