DB2 - Problem description
Problem IC64509 | 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 / 910 - 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: * * 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 | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows | |
Solution | |
Problem was first first fixed in Version 9.1 Fixpak 9 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC65138 IC65139 IZ66828 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.11.2009 19.04.2010 19.04.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.0., 9.1. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.9 |