|
Problem IC77587
|
Status: Closed |
LOCK_TIMEOUT_VAL FROM LOCKING EVENT MONITOR IS INCORRECT WHEN L OCK WAIT OCCURSBEFORE LOCK TIMEOUT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
lock_timeout_val from locking event monitor is incorrect when
lock wait occurs
before lock timeout
If both Lock Wait and Lock timeout alerts are configured for 9.7
db using locking event monitor,
then a lock wait event occurs and later the same waiter gets a
timeout.
The Lock Timeout event will have the wrong value for
LOCK_TIMEOUT_VAL. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All platfrom. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See APAR Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP5. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
DB2 V9.7 FP5 will contain the fix. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.07.2011
22.12.2011
22.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
