|
Problem IC61676
|
Status: Closed |
ANY INTERNAL DB MGR COMPONENT ISSUEING CATALOG TABLE UPDATE FROM NON-CATALOG NODE,CAUSE BAD LOCK NAME MAY LEAD TO CONCURENCY |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Any internal Database Manager components that issue a catalog
table update from a non-catalog node, may end up with the bad
lock name.
The bad lock name can lead to unexpected lock timeouts or even
deadlocks.
The APAR should be identifiable by the bad lockname itself ie
Lock Name: 00000000000000000000000043
Even utilities that are issued from the catalog node initially
like runstats, may internally drive an update from the
non-catalog node. |
| Problem Summary: |
ANY INTERNAL DB MGR COMPONENT ISSUEING CATALOG TABLE UPDATE
FROM NON-CATALOG NODE,CAUSE BAD LOCK NAME MAY LEAD TO CONCURENCY |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in V97 FP1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.06.2009
05.02.2010
05.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
