Which authority or privilege is granted by the DB2 Database Manager configuration file?
A. CONNECT
B. CONTROL
C. SYSMAINT
D. EXECUTE
2 Comments on “Which authority or privilege is granted by the DB2 Database Manager configuration file?”
kwsays:
A user with SYSMAINT authority can do the following:
Query the state of a table space
Update log history files
Quiesce a table space
Reorganize a table
Collect catalog statistics using the RUNSTATS utility.
0
0
Chow, Kenneth KYsays:
DB2 9 has the ability to specify different authentication mechanisms depending on whether the
user is attempting to connect to the database, or perform instance attachments and instance level
operations. By default, the instance is set up to use one type of authentication for all instance
level and connection level requests. This is specified by the Database Manager Configuration
parameter AUTHENTICATION. Introduced in V9.1 is the Database Manager Configuration
parameter SRVCON_AUTH. This parameter specifically deals with connections to databases. So,
for example, if you have the following set in your DBM CFG:
DB2 GET DBM CFG
Server Connection Authentication (SRVCON_AUTH) = KERBEROS
Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT
A user with SYSMAINT authority can do the following:
Query the state of a table space
Update log history files
Quiesce a table space
Reorganize a table
Collect catalog statistics using the RUNSTATS utility.
0
0
DB2 9 has the ability to specify different authentication mechanisms depending on whether the
user is attempting to connect to the database, or perform instance attachments and instance level
operations. By default, the instance is set up to use one type of authentication for all instance
level and connection level requests. This is specified by the Database Manager Configuration
parameter AUTHENTICATION. Introduced in V9.1 is the Database Manager Configuration
parameter SRVCON_AUTH. This parameter specifically deals with connections to databases. So,
for example, if you have the following set in your DBM CFG:
DB2 GET DBM CFG
Server Connection Authentication (SRVCON_AUTH) = KERBEROS
Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT
0
0