home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC96022 Status: Geschlossen

POTENTIAL HANG ON TRANENTRY LATCH IN SQLPM_WRITE_APPL_LOCKS DURING LOCK
SNAPSHOT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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')
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 10.1 Fix Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.09.2013
02.06.2014
02.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList