1  –  ALL_PRIVILEGES

    Specifies that SQL should grant all privileges to the specified
    users.

2  –  ON object-type

    Syntax options:

       ON DATABASE ALIAS alias
       ON TABLE table-name
       ON TABLE view-name
       ON MODULE module-name
       ON FUNCTION routine-name
       ON PROCEDURE routine-name
       ON SEQUENCE sequence-name

    Specifies whether the GRANT statement applies to ACLs for the
    named object. 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.

    Specifies whether the GRANT statement applies to ACLs for all
    objects of the specified type. If privileges are denied for the
    operation on some objects, then the GRANT is aborted.

3  –  privileges

    Type of privileges:

       db-privs-ansi
       table-privs-ansi
       column-privs-ansi
       module-privs-ansi
       ext-routine-privs-ansi
       sequence-privs-ansi

 Specifies the set of privileges you want to add to an existing
 access privilege set entry or create in a new one. The operations
 permitted by a given privilege keyword differ, depending on whether
 you granted it for a database, table, column, module, or external
 routine. The Privileges Table (in the GRANT) lists the privilege
 keywords and their meanings for databases, tables, columns, modules,
 external routines and sequences.

4  –  role-name

    The name of a role, such as one created with the CREATE ROLE
    statement. If the role name exists as an operating system group
    or rights identifier, then Oracle Rdb will create the role
    automatically when you issue the GRANT statement. A role that
    is created automatically always has the attribute of IDENTIFIED
    EXTERNALLY.

5  –  TO identifier ansi style

    Specifies the identifiers for the new or modified access
    privilege set entry. Specifying PUBLIC is equivalent to a
    wildcard specification of all user identifiers.

    In ANSI/ISO-style databases, you are allowed to specify only
    single-user user identifiers; no general or system identifiers
    are allowed. Access privilege set entries identify only those
    users who are common to all groups defined by the individual
    identifiers. Users who do not match all identifiers are not
    controlled by that entry. ANSI/ISO-style access privilege sets
    support only user identifiers.

6  –  user-identifier

    Specifies a user identifier that uniquely identifies each user on
    the system.

    On OpenVMS, 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 an ANSI/ISO-style database, the creator
    of the database gets all privileges, and the PUBLIC entry gets no
    privileges.

    In an ANSI/ISO-style database, you cannot use multiple user
    identifiers.

    In ANSI/ISO-style user identifiers, the only wildcard allowed is
    in the public identifier [*,*].

    For more information about identifiers, see the OpenVMS operating
    system documentation.

7  –  WITH_GRANT_OPTION

    Allows the user who has been granted a privilege the option of
    granting that privilege to other users.

    The WITH GRANT OPTION clause specifies that the grantees in the
    TO clause may grant the privileges in the privilege list to other
    users for as long as they have the privileges. When the privilege
    is revoked from the grantee who received the privileges with
    the WITH GRANT OPTION clause, the privileges also are revoked
    from all the users who received the privileges from that grantee
    (unless these users have received the privilege from yet another
    user who still has the privilege).