![]() The group itself is controlled through the security facility used on the workstation where the instance has been defined. Sysadm_group parameter of the DB2 Database Manager configuration file associated with a particular instance. SYSADM authority can only be assigned to a group, and this assignment is made by storing the appropriate group name in the Take away (revoke) Database Administrator authority from groups and/or individual users. Give (grant) Database Administrator authority to groups and/or individual users. To control the amount of system resources allocated to a single instance.) (The DB2 Database Manager configuration file is used Which groups have System Control and/or System Maintenance authority. Modify the parameter values of the DB2 Database Manager configuration file associated with the instance-including specifying Migrate an existing database to make it compatible with a new version of DB2 UDB. In addition, users who have been given this authority are allowed to perform the following tasks: Tables, views, indexes, schemas, aliases, data types, functions, procedures, triggers, packages, servers, and event monitors. Users that have been given this authority are allowed to run any available DB2 UDB utilities, execute any DB2 UDB command, perform any SQL operation, and control all objects within an instance, including databases, database partition groups, buffer pools, tablespaces, System Administrator (SYSADM) authority is the highest level of administrative authority available with DB2 UDB. Conversely, the two database-level authoritiesĬan be assigned to an individual user and/or to a group of users groups and users that have been assigned database-levelĪuthorities are recorded in the system catalog tables of the database to which the authority applies. ![]() Furthermore, the three instance-levelĪuthorities can only be assigned to groups the names of the groups that are assigned these authorities are stored in theĭB2 Database Manager configuration file that is associated with the instance. Instance), while the remaining two apply only to specific databases within an instance. The first three of these levels apply to the DB2 Database Manager instance (and to all databases that are managed by that AuthoritiesĭB2 UDB uses five different levels of authority to control how users perform administrative and/or maintenance operations againstĪn instance or a database. Hierarchy of the authorities and privileges available with DB2 UDB. Figure 3-3 provides a hierarchical view of the authorities and privileges that are recognized by DB2 UDB.įigure 3-3. Users can only work with those objects for which they have been given the appropriate authorization-that ![]() ![]() To the DB2 Database Manager for an instance, to one or more databases running under that instance's control, and to a particularĭatabase's objects. Together, authorities and privileges act to control access Privileges, on the other hand, convey the rights to perform certain actionsĪgainst specific database resources (such as tables and views). ![]() Operations against an instance or a database. Authorities convey a set of privileges and/or the right to perform high-level administrative and maintenance/utility Privileges that have been assigned to a group the user is a member of) to determine what operations the user is allowed to Once a user has been authenticated and an attachment to an instance or a connection to a database has been established, theĭB2 Database Manger evaluates any authorities and privileges that have been assigned to the user (these can be assigned directly to a user, or they can be obtained indirectly from group Learn More Buy Authorities and Privileges DB2 Universal Database V8.1 Certification Exam 700 Study Guide ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |