home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65138 Status: Geschlossen

IN DPF, CONNECTING TO A QUIESCED DATABASE BY A USER WHO HAS
QUIESCE_CONNECT AUTHORITY MAY STILL THROW A SQL20157N ERROR

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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 bysettingDB2NODE to another partition would  fail   * 
* with SQL20157Nerror though the user 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          * 
* 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.5 Fixpak 6 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
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.5 Fixpak 6
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
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.12.2009
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version