|
Problem IC65139
|
Status: Closed |
IN DPF, CONNECTING TO A QUIESCED DATABASE BY A USER WHO HAS QUIESCE_CONNECT AUTHORITY MAY STILL THROW A SQL20157N ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In DPF environments, After granting quiesce_connect on the
database to the user and even to its group, if the instance is
quiesced as follows "db2 quiesce instance <instancename> group
cmodprod immediate", connect to the database by setting DB2NODE
to another partition would fail with SQL20157N error though
theuser has quiesce_connect authority.
For example:
db2 "grant quiesce_connect on database to user usr1"
db2 "grant quiesce_connect on database to group grp1"
db2 quiesce instance <instancename> group grp1 immediate
As usr1:
export DB2NODE=1
db2 terminate
db2 connect to <dbname>
SQL20157N User "usr1 " does not have the QUIESCE_CONNECT
privilege. SQLSTATE=08004 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DPF users *
****************************************************************
* PROBLEM DESCRIPTION: *
* In DPF environments, After granting quiesce_connect on *
* thedatabase to the user and even to its group, if the *
* instanceisquiesced as follows "db2 quiesce instance *
* <instancename>group cmodprod immediate", connect to the *
* database bysetting DB2NODE to another partition would fail *
* withSQL20157N error though the user has *
* quiesce_connectauthority.For example:db2 "grant *
* quiesce_connect on database to user usr1"db2 "grant *
* quiesce_connect on database to group grp1"db2 quiesce *
* instance <instancename> group grp1 immediateAs usr1:export *
* DB2NODE=1db2 terminatedb2 connect to <dbname>SQL20157N User *
* "usr1 " does not have the QUIESCE_CONNECTprivilege. *
* SQLSTATE=08004 *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to Version 9.7 Fixpak 2 or later *
**************************************************************** |
| Local Fix: |
Invoke the quiesce command using the user option instead for
every user belonging to the group.
db2 quiesce instance <inst_name> user usr1 immediate |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fixpak 2 |
| Workaround |
Invoke the quiesce command using the user option instead for
every user belonging to the group.
db2 quiesce instance <inst_name> user usr1 immediate |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.12.2009
22.06.2010
22.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
