Bug 1104382 - Errors in documentation of Oracle database permission configuration
Summary: Errors in documentation of Oracle database permission configuration
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite Proxy 5
Classification: Red Hat
Component: Docs Installation Guide
Version: unspecified
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: ---
Assignee: David O'Brien
QA Contact: Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks: sat-docs
TreeView+ depends on / blocked
 
Reported: 2014-06-03 21:31 UTC by Umar Nadeem
Modified: 2014-10-20 07:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-20 07:59:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Umar Nadeem 2014-06-03 21:31:29 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
Build Identifier: 

The words "specific" are used to incorrectly in the document to refer to either "explicit" or "role-based" permissions. The words don't translate in the doc. 

Reproducible: Always

Comment 4 Umar Nadeem 2014-07-07 13:12:00 UTC
I am providing the full comments of the customer. It looks like there's a mistake in using the right terms but maybe this might give you more context to work with.


Comments:

"Red Hat documentation is pretty detailed and easy to follow. However, we have had very big issues with one particular document regarding Oracle database permission configuration (satellite). Using actual technical terms when referencing other technologies, for example: Oracle Database permissions. There is no such thing as "specific". Oracle database permissions are either explicit or role-based. When Oracle DBAs read "specific" it doesn't translate."

Hope this helps.

Comment 7 David O'Brien 2014-10-20 07:59:49 UTC
"specific" occurs twice in other contexts.
"Oracle" occurs once in the Legal Notice.
"database" occurs not at all.

Without specific information I can't fix anything.


Note You need to log in before you can comment on or make changes to this bug.