|
Problem IC88357
|
Status: Closed |
ANONYMOUS BLOCK DEADLOCK OCCURS WHEN RUNSTATS IS PERFORMED PREVIOUSLY IN THE SAME TRANSACTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 FP2 or subsequent fix pack. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
First Fixed in DB2 Version 10.1 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.11.2012
17.01.2013
17.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
