Document least privilege model as alternative to SYSDBA for Oracle co…

[brandonwest-netwrix]

clarify actual Oracle Data collection permissions

Gives writers a lower-privilege option for Oracle data collection instead of requiring the SYSDBA role.

Generated with AI

[github-actions]

Documentation PR Review

Editorial Review

docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md

• Structure — Line 46: The new inline link to the Least Privilege Model duplicates the existing cross-reference just two lines below ("There is a least privilege model for scanning your domain. See the [Oracle Target Least Privilege Model]... topic"). Readers encounter the same destination twice within a few lines. Suggested fix: keep the recommendation on the bullet without the inline link and let the existing cross-reference paragraph point readers to the topic — or remove the standalone paragraph and keep only the inline link. Avoid presenting both.
• Clarity — Line 46: The bolded label "Recommmended" floats at the start of the bullet with no grammatical connection to the rest of the line, and it's ambiguous whether it applies to the SYSDBA role, the Least Privilege Model, or both options. (Note the word is also misspelled — three m's.) Suggested fix: "User with the SYSDBA role (recommended) or the Least Privilege Model."
• Clarity — Line 46: "OR" is set in all caps, which reads as shouting/emphasis rather than a neutral conjunction. Suggested fix: use lowercase "or".

docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md

• Structure — Line 46: The new inline link to the Least Privilege Model duplicates the existing cross-reference just two lines below ("There is a least privilege model for scanning your domain. See the [Oracle Target Least Privilege Model]... topic"). Readers encounter the same destination twice within a few lines. Suggested fix: keep the recommendation on the bullet without the inline link and let the existing cross-reference paragraph point readers to the topic — or remove the standalone paragraph and keep only the inline link. Avoid presenting both.
• Clarity — Line 46: The bolded label "Recommmended" floats at the start of the bullet with no grammatical connection to the rest of the line, and it's ambiguous whether it applies to the SYSDBA role, the Least Privilege Model, or both options. (Note the word is also misspelled — three m's.) Suggested fix: "User with the SYSDBA role (recommended) or the Least Privilege Model."
• Clarity — Line 46: "OR" is set in all caps, which reads as shouting/emphasis rather than a neutral conjunction. Suggested fix: use lowercase "or".

Summary

6 editorial suggestions across 2 files. Both files received the same one-line change, so the suggestions mirror each other. Vale and Dale issues are auto-fixed separately.

---

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

[github-actions]

Auto-Fix Summary

4 issues fixed, 4 skipped across 2 files

Category	Fixes
Substitutions	2
Dale: passive-voice	2

Skipped (needs manual review)	Reason

| docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md:47 — Dale: xy-slop | 'Only applies to Windows Servers and not on Linux or Unix operating systems' is a positive-first scoping clarification, not the 'x is not y, x is z' negative-first reversal the rule targets; rewriting risks changing the intended scope. |
| docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md:50 — Dale: wordiness | 'There is a least privilege model for scanning your domain.' is mildly wordy, but a concise rewrite risks altering meaning or creating redundancy with the preceding bullet. |
| docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md:47 — Dale: xy-slop | 'Only applies to Windows Servers and not on Linux or Unix operating systems' is a positive-first scoping clarification, not the 'x is not y, x is z' negative-first reversal the rule targets; rewriting risks changing the intended scope. |
| docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md:50 — Dale: wordiness | 'There is a least privilege model for scanning your domain.' is mildly wordy, but a concise rewrite risks altering meaning or creating redundancy with the preceding bullet. |

Ask @claude on this PR if you'd like an explanation of any fix.