DB2 FOR LUW / DB2FORLUW / 970 - DB2

DB2 may abend in  SQLECLEANUPFEDDAEMONANCHOR()->GETIDENTITY() 
call due to the timing window exist during federated system 
initialization. 
 
The stacks can actually vary but the idea is that we come in 
function sqleCleanupFedDaemonAnchor() with the stack similar to 
the following: 
 
  SQLO_SLATCH_CAS64::getIdentity() 
  sqleCleanupFedDaemonAnchor() 
  sqleFedFMPManager() 
  sqeApplication::TermApplication() 
  sqeAppServices::DestroyAppl() 
  sqleExecuteNodeRecovery()

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fixpak 7                                  * 
****************************************************************

n/a

DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 9.7 Fixpak 7

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC87899 IC89553 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

31.05.2012
13.11.2012
13.11.2012

9.7.