DBADM administrative authority

With the DBADM authority, you can also perform the following actions:

• Drop or alter any table space, table, or index in the database
• Issue a COMMENT, LABEL, or LOCK TABLE statement for any table in the database
• Issue a COMMENT statement for any index in the database
• Drop a view created for another user when you have the DBADM authority on the database that contains the base table
• Select from a view without always requiring system level authority

If the value of the DBACRVW subsystem parameter is set to YES during the Db2 installation, an ID with the DBADM authority can complete the following tasks:

• Create a view for another authorization ID on tables in that database.
• Create a materialized query table or alter a table to become a materialized query table for another authorization ID. This action requires that DBADM authority is held on the database in which the tables of the fullselect reside and that the authorization ID has DBADM authority on the database in which the materialized query table is to reside.
• Create an alias for itself or another authorization ID for a table in that database.
• Drop a view. This action requires that the base objects contain at least one table and the DBADM authority on the database that contains the table.

For more information, see DBADM CREATE AUTH field (DBACRVW subsystem parameter).

An ID with DBADM authority on one database can create a view on tables and views in that database and other databases only if the ID has all the privileges that are required to create the view. For example, an ID with DBADM authority cannot create a view on a view that is owned by another ID.

If a user has the DBADM authority with the GRANT option, that user can grant these privileges to others.

The following tables summarizes any included authorities, and privileges held and grantable to others, by the DBADM administrative authority.