DB2 FOR LUW / DB2FORLUW / 970 - DB2

When a federated server utilizing two-phase-commit starts up it 
will hold the tranEntry latch.  If the federated query involves 
connecting back into the same database then it will start an 
agent that will try to get the dblatch. 
 
Since snapshot processing first gets the dblatch and then tries 
to get the tranEntry latch, it is possible for a hang to occur 
if a LOCK snapshot is processing when such federated query 
processing is running.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Anybody using federated transaction two phase commit         * 
* transaction and LOCK snapshots                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 9                            * 
****************************************************************

This hang can be avoided if the federated transaction does not 
require two phase commit. Two phase commit can be disabled as 
follows: 
 
alter server <server name> options (set DB2_TWO_PHASE_COMMIT 
'N')

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
 

Problem was first fixed in Version 9.7 Fix Pack 9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC96022 IC96028 IC96535 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

17.09.2013
16.12.2013
16.12.2013

9.7.FP9