|
Problem IC64509
|
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 / 910 - 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: *
* Users in a DPF Environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* IN DPF, CONNECTING TO A QUIESCED DATABASE BY A USER WHO HAS *
* QUIESCE_CONNECT AUTHORITY MAY STILL THROW A SQL20157N ERROR *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.1 Fixpak 9 *
* or *
* Use the workaround listed *
**************************************************************** |
| 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.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Lösung |
Problem was first first fixed in Version 9.1 Fixpak 9 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC65138 IC65139 IZ66828
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 11.11.2009
19.04.2010
19.04.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.0.,
9.1.
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.9
|
 |
