|
Problem IC85446
|
Status: Closed |
ANONYMOUS BLOCK DEADLOCK OCCURS WHEN RUNSTATS IS PERFORMED PREVIOUSLY IN THE SAME TRANSACTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When a parent transaction performs runstats, it acquires catalog
cache X locks and holds them until the end of UOW. Within the
same parent transaction, before runstats, an Anonymous Block is
prepared and an i-coord is forked off to handle a separate
transaction, but it waits for the catalog cache locks held by
its parent transaction. This results in an Anonymous Block
deadlock. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 FP7 or subsequent fix pack *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
Problem First Fixed in DB2 Version 9.7 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC88357
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.07.2012
23.10.2012
23.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
