RDBPROD: Hints and Tips on solving RDB-E-NO_PRIV problems for Users.
(Doc ID 859971.1)
Last updated on FEBRUARY 06, 2020
Applies to:Oracle Rdb Server on OpenVMS - Version 7.0 and later
HP OpenVMS Alpha
HP OpenVMS VAX
HP OpenVMS Itanium
Possible reasons and corrective actions for " %RDB-E-NO_PRIV, privilege denied by database facility"
Oracle Rdb has internal security checks to control who is able to access or change objects within the database, ranging from opening a database to updating a table. Chapter 9 in the Oracle Rdb7 Guide to Database Design and Definition (<Note:133454.1>) describes in detail the security mechanisms inside the database, with Table 9-1 listing privileges required for almost every DDL or DML activity. Table 1-1 in the Oracle Rdb RMU Reference Manual (<Note:133454.1>) lists RMU privileges and OpenVMS override privileges for activities including opening or closing a database.
By default the security is OpenVMS ACL style, where access can be granted or denied using a UIC which can be a name, such as [DATABASE,USER1], numeric, such as [20,1], or a rights identifier. Access may also come through wildcard UIC settings [*,*].
The examples below will focus on solutions involving a UIC. Use the OpenVMS utility AUTHORIZE to discover UIC values for accounts or ask the user who is having the problem to perform a $SHOW PROCESS.
The purpose of this article is to help determine what to do in order to allow a user to access a database. It does not cover privilege errors manipulating metadata.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document