GRANT (buffer pool privileges) statement

This form of the GRANT statement grants privileges on a buffer pool.

Invocation

This statement can be embedded in an application program or issued through the use of dynamic SQL statements. It is an executable statement that can be dynamically prepared only if DYNAMICRULES run behavior is in effect for the package (SQLSTATE 42509).

Authorization

The privileges held by the authorization ID of the statement must include at least one of the following authorities: ACCESSCTRL or SECADM authority.

Syntax

Read syntax diagramSkip visual syntax diagramGRANT USE ON BUFFERPOOLbuffer-pool-name TO,USERGROUPROLEauthorization-name

Description

USE ON
Grants the privilege to use the buffer pool for table spaces.
BUFFERPOOL buffer-pool-name
Identifies the buffer pool on which the USE privilege is to be granted.
TO
Specifies to whom the USE privilege is granted.
USER
Specifies that the authorization-name identifies a user.
GROUP
Specifies that the authorization-name identifies a group.
ROLE
Specifies that the authorization-name identifies a role name. The role name must exist at the current server (SQLSTATE 42704).
authorization-name
Lists the authorization IDs of one or more users, groups, or roles.

The list of authorization IDs cannot include the authorization ID of the user issuing the statement (SQLSTATE 42502).

Rules

  • For each authorization-name specified, if neither USER, GROUP, nor ROLE is specified, then:
    • If the security plug-in in effect for the instance cannot determine the status of the authorization-name, an error is returned (SQLSTATE 56092).
    • If the authorization-name is defined as ROLE in the database, and as either GROUP or USER according to the security plug-in in effect, an error is returned (SQLSTATE 56092).
    • If the authorization-name is defined according to the security plug-in in effect as both USER and GROUP, an error is returned (SQLSTATE 56092).
    • If the authorization-name is defined according to the security plug-in in effect as USER only, or if it is undefined, USER is assumed.
    • If the authorization-name is defined according to the security plug-in in effect as GROUP only, GROUP is assumed.
    • If the authorization-name is defined in the database as ROLE only, ROLE is assumed.

Examples

The following example shows the command syntax for granting the user, AMY, the ability to use the buffer pool BP1:
GRANT USE ON BUFFERPOOL BP1 TO USER AMY