You must invoke a database before you issue the SHOW PRIVILEGES
    statement.

    The display for the SHOW PRIVILEGES statement reflects
    information stored following a COMMIT or ROLLBACK statement
    and a detach from the database with a FINISH statement. Unlike
    the SHOW PROTECTION statement, SHOW PRIVILEGES will not reflect
    uncommitted changes. Any changes you make to your privileges or
    those of other users do not take effect until you detach from the
    database.

    In order to perform a certain operations, you must have
    the correct access mode privilege (READ, WRITE, MODIFY, or
    ERASE) on both the database and the relation. Therefore, the
    SHOW PRIVILEGES display for a relation will drop any access
    mode privileges that are not present for the database before
    displaying the privileges for the relation.

    If you hold one or more of the OpenVMS override privileges
    (SYSPRV, OPER, or SECURITY) or one or more of the Oracle Rdb role-
    oriented privileges (ADMINISTRATOR, OPERATOR, or SECURITY),
    you are implicitly granted privileges to database objects as
    a result of an ACL override. You operate as if you actually
    hold the privileges you are implicitly granted, even though
    these privileges are not stored in the ACL. The SHOW PRIVILEGES
    statement displays the privileges you have to a database object
    as a result of holding the OpenVMS override privilege or Oracle Rdb
    role-oriented privilege.

    The SHOW PRIVILEGES statement displays only those privileges that
    are valid for the database object. For example, although you may
    hold the Oracle Rdb ADMINISTRATOR, OPERATOR, or SECURITY database
    privileges, these privileges are not displayed when you issue
    the SHOW PRIVILEGES statement for a relation because they are not
    relation privileges.