|
Problem IC87899
|
Status: Closed |
POSSIBLE CRASH/SEGV IN SQLECLEANUPFEDDAEMONANCHOR()->GETIDENTITY() DUE TO TIMING ISSUE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 V10.1 Fixpak 2 *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V10.1 Fixpak 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
24.04.2013
24.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
