home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC62841 Status: Closed

TRAP RESILIENCE CODE CAUSE DEADLATCH BETWEEN SNAPSHOT AND XA
COMMIMT/ROLLBACK

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Deadlatch is observed during test,  a monitor thread holds the 
masterAppLatch (stabilizing application list), and as it 
iterates through all apps, it will acquire/release the 
transEntryLatch for each application in order to dump a stable 
picture of the locks held by the app; meanwhile, another thread 
doing XA commit processing is holding the latches in reverse 
order -- it's holding the transEntrylatch because it hasn't 
committed, and it can't commit until it updates the application 
status, for which it needs the master app latch. The XA thread, 
tries to update the application status in 
sqlrr_end_tran_after_DPS() ( trap resilience's code  ), so this 
is a new deadlatch scenario.
Problem Summary:
Problem Description: 
TRAP RESILIENCE CODE CAUSE DEADLATCH BETWEEN SNAPSHOT AND XA 
COMMIMT/ROLLBACK 
Problem Summary: 
Deadlatch is observed during test,  a monitor thread holds the 
masterAppLatch (stabilizing application list), and as it 
iterates through all apps, it will acquire/release the 
transEntryLatch for each application in order to dump a stable 
picture of the locks held by the app; meanwhile, another thread 
doing XA commit processing is holding the latches in reverse 
order -- it's holding the transEntrylatch because it hasn't 
committed, and it can't commit until it updates the application 
status, for which it needs the master app latch. The XA thread, 
tries to update the application status in 
sqlrr_end_tran_after_DPS() ( trap resilience's code  ), so this 
is a new deadlatch scenario.
Local Fix:
n/a
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows

Solution
Problem is first fixed in Version 9.7 Fix Pack 1
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.08.2009
21.12.2009
21.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList