DB2 - Problem description
Problem IC96022 | Status: Closed |
POTENTIAL HANG ON TRANENTRY LATCH IN SQLPM_WRITE_APPL_LOCKS DURING LOCK SNAPSHOT | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Anybody using federated transaction two phase commit * * transaction and LOCK snapshots * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
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') | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 10.1 Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.09.2013 02.06.2014 02.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |