|
Problem IT07868
|
Status: Closed |
THRESHOLD TOTALMEMBERCONNECTIONS IS ENFORCED FOR USERS WITH DBADM OR WLMADM AUTHORITY. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1FP5 *
**************************************************************** |
| Local Fix: |
|
| Solution |
The problem is first fixed in DB2 version 10.1 Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.03.2015
28.07.2015
28.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
