|
Problem IC87899
|
Status: Geschlossen |
POSSIBLE CRASH/SEGV IN SQLECLEANUPFEDDAEMONANCHOR()->GETIDENTITY() DUE TO TIMING ISSUE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 Fixpak 2 *
**************************************************************** |
| Local-Fix: |
n/a |
| verfügbare FixPacks: |
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
|
| Lösung |
First fixed in DB2 V10.1 Fixpak 2 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 04.11.2012
24.04.2013
24.04.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
