DB2 FOR LUW / DB2FORLUW / A50 - DB2

During the activate/deactivate database with an user who has 
DBADM authority, the threshold behavior is not compatible 
with the documentation: 
 
TOTALMEMBERCONNECTIONS > integer-value 
 
This condition defines an upper bound on the number of 
coordinator connections that can run concurrently on a member. 
This value 
can be zero or any positive integer (SQLSTATE 42820). A value of 
zero 
means that any new coordinator connection will be prevented from 
connecting. 
All currently running or queued connections will continue. The 
definition domain for this condition must be DATABASE, and the 
enforcement scope must be MEMBER (SQLSTATE 5U037). This 
threshold is not enforced for users with DBADM or WLMADM 
authority 
 
But in this case threshold is exceeded even though instance 
owner have 
a DBADM authority: 
 
db2 "CREATE THRESHOLD DB_PREVENT_NEW_CONNECTIONS FOR DATABASE 
ACTIVITIES^JENFORCEMENT MEMBER WHEN TOTALMEMBERCONNECTIONS > 0 
STOP EXECUTION" 
db2 "quiesce db defer with timeout 15" 
db2 terminate 
DB20000I  The TERMINATE command completed successfully. 
db2 deactivate database ttest 
DB20000I  The DEACTIVATE DATABASE command completed 
successfully. 
 
 db2 activate database ttest 
SQL4712N  The threshold "DB_PREVENT_NEW_CONNECTIONS" has been 
exceeded. 
Reason code = "2".  SQLSTATE=5U026

**************************************************************** 
* USERS AFFECTED:                                              * 
* Everyone who encounters the problem                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v105fp7                                       * 
****************************************************************

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

23.04.2015
21.01.2016
21.01.2016