home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80891 Status: Geschlossen

WHEN STARTING LOAD EDU, MAY HANG DUE TO ACCESSING UNINITIALIZED LATCH
MEMORY FOR AGENTCBLATCH

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When LOAD EDU is started, the failed initialization of 
memory used for a latch ( latch is for controlling, serializing 
access to edu's control block ) can lead to a hang. This 
causes load EDU to wait forever for latch that nobody is 
holding. 
 
Stacks shows: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x090000000F930C20 sqloXlatchConflict + 0x68 
0x090000000F930ABC sqloXlatchConflict@glue161 + 0x74 
0x090000000FBAC900 AgentSetPriority__8sqeAgentFiT1 + 0x224 
0x0900000010CC1AE0 
@146@sqleServiceClassMapAgent__FP18SQLE_SERVICE_CLASSP8sqeAgent 
+ 0x24C 
0x09000000104E5B9C 
sqluInitLoadEDU__FP8sqeAgentPP8sqeAgentPUcP8SQLRXNLSP13SQLUCACB_ 
TYPEP13SQLO_MEM_POOL + 0x1340 
0x090000001051BE70 sqlulbuf__FPUcUi + 0x244 
0x090000000FA13688 sqloEDUEntry + 0x49C 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.7 and above                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Load EDU, when started, fail to initialize  memory portion   * 
* which is used for latch ( latch is for controlling ,         * 
* serializing access to edu's control block ). This cause      * 
* load's EDU to wait forever for latch that nobody holding.    * 
*                                                              * 
* Stacks shows:                                                * 
*                                                              * 
* <StackTrace>                                                 * 
* -------Frame------ ------Function + Offset------             * 
* 0x090000000F930C20 sqloXlatchConflict + 0x68                 * 
* 0x090000000F930ABC sqloXlatchConflict@glue161 + 0x74         * 
* 0x090000000FBAC900 AgentSetPriority__8sqeAgentFiT1 + 0x224   * 
* 0x0900000010CC1AE0                                           * 
* @146@sqleServiceClassMapAgent__FP18SQLE_SERVICE_CLASSP8sqeAg * 
* ent + 0x24C                                                  * 
* 0x09000000104E5B9C                                           * 
* sqluInitLoadEDU__FP8sqeAgentPP8sqeAgentPUcP8SQLRXNLSP13SQLUC * 
* ACB_TYPEP13SQLO_MEM_POOL + 0x1340                            * 
* 0x090000001051BE70 sqlulbuf__FPUcUi + 0x244                  * 
* 0x090000000FA13688 sqloEDUEntry + 0x49C                      * 
* </StackTrace>                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to fixpack containing this fix                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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

Lösung
Upgrade to fixpack containing this fix
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.01.2012
12.06.2012
12.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.6 FixList