|
Problem IC83872
|
Status: Closed |
POSSIBLE CRASH/SEGV IN SQLECLEANUPFEDDAEMONANCHOR()->GETIDENTITY() DUE TO TIMING ISSUE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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() |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 Fixpak 7 *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
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
|
| Solution |
First fixed in DB2 9.7 Fixpak 7 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC87899 IC89553
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.05.2012
13.11.2012
13.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
