1 – ALL_PRIVILEGES
Specifies that SQL should revoke all privileges in the access
privilege set entry.
2 – FROM
Syntax options:
FROM identifier-ansi-style
FROM PUBLIC
Specifies the identifiers for the access privilege set entry
to be modified or deleted. Specifying PUBLIC is equivalent to a
wildcard specification of all user identifiers.
The only identifiers are ones that translate to an OpenVMS user
identification code (UIC).
For more information about user identifiers, see the operating
system documentation.
Syntax options:
ON DATABASE alias
ON TABLE table-name
ON COLUMN column-name
ON MODULE module-name
ON FUNCTION ext-routine-name
ON PROCEDURE ext-routine-name
ON SEQUENCE sequence-name
Specifies whether the REVOKE statement applies to ACLs for database
objects. You can specify a list of names for any form of the ON
clause. You must qualify a column name with at least the associated
table name.
3 – ON
Syntax options:
ON DATABASE *
ON MODULE *
ON FUNCTION *
ON PROCEDURE *
ON SEQUENCE *
Specifies whether the REVOKE statement applies to ACLs for all
objects of the specified types. If privileges are denied for the
operation on some objects, then the REVOKE is aborted.
4 – privileges
Types of privileges:
db-privs-ansi
table-privs-ansi
column-privs-ansi
module-privs-ansi
ext-routine-privs-ansi
sequence-privs-ansi
Specifies the list of privileges you want to remove from an
existing access privilege set entry. The operations permitted
by a given privilege keyword differ, depending on whether it
was granted for a database, table, column, module, routine, or
sequence. The Privileges Table in the GRANT lists the privilege
keywords and their meanings for databases, tables, modules,
external routines and sequences.
5 – user-identifier
Uniquely identifies each user on the system.
The user identifier consists of the standard OpenVMS user
identification code (UIC), a group name, and a member name (user
name). The group name is optional. The user identifier can be
in either numeric or alphanumeric format. The following are all
valid user identifiers that could identify the same user:
K_JONES
[SYSTEM3, K_JONES]
[341,311]
When Oracle Rdb creates a database, it automatically creates an
access privilege set entry with the PUBLIC identifier, which
grants all privileges except DBCTRL to any user. In access
privilege set databases, the only wildcard allowed is the PUBLIC
identifier.
You cannot use more than one user identifier in a multiple
identifier.