DB2 10.5 for Linux, UNIX, and Windows

Internal system-defined routine

When Security Administrator (SECADM) users GRANT privileges to individual routines for users, SECADM users might come across certain internal routines. When users do not have the required privileges for these internal routines, operations that require the privilege of these internal routines might fail.

This table can be useful when deploying a restrictive database. Users can encounter missing privilege errors on certain internal routines. SECADM must consult this table and the routine description to decide whether they need to grant EXECUTE privilege on the specific internal routine that is failing with an authorization error.

This table can also be useful when the SECADM is trying to harden/secure a non-restrictive database. After you receive the report of privileges on internal routines that are granted to the special group PUBLIC, a SECADM user can consult this table to decide which internal routines still need EXECUTE privilege granted to specific users, roles, or groups.

These internal routines, their respective description, and the appropriate criteria to use them in a GRANT statement are as follows:

Table 1. Internal system-defined routine needed by non-SECADM users
Routine Name Description