|
Problem IC84126
|
Status: Closed |
WLM INCORRECTLY BLOCKS RESYNC REQUEST |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
DRDA RESYNC request can drive a database connection without
group/user authorization ID.
Then later when WLM (Workload Manager) perform workload
assignment, it will detect
that no privilege to use for any of the workload
(as no user id is specified), and it reports a -4707 error
As for example, this can happen against a DB2 z/OS resync
request to DB2 LUW and the DB2 zOS log will get an error.
The fix is done at DB2 LUW WLM side to skip privilege check when
it uses RESYNC.
The DB2 zOS side log will show messages similar to following :
14.56.01 S0021304 DSNV401I -DP37 DISPLAY THREAD REPORT FOLLOWS
-
14.56.01 S0021304 DSNV406I -DP37 INDOUBT THREADS - 641
641 COORDINATOR STATUS RESET URID AUTHID
641 DP3G COMMITTED 212DAD430D31 LUPBPRD
641 V467-HAS LUWID <>.<>.C68E8937E346.59F7=53880
641 V450-HAS PARTICIPANT INDOUBT AT
641 CLMPRDP1-::FFFF:<ip-address>..50000
641 DISPLAY INDOUBT REPORT COMPLETE |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 FP1 or subsequent fix pack *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem First Fixed in DB2 Version 10.1 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
13.11.2012
13.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
