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 IT01858 Status: Geschlossen

TRAP IN SQLEGWRT FUNCTION DUE TO MEMORY ACCESS VIOLATION IN MULTI-THREADED
ENVIRONMENT.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
While running applications in a multi-threaded environment, a 
memory access violation in sqlegwrt function could result in a 
trap with a stack trace similar to the following: 
sqlegwrt 
write_it_dwrt 
sqledwrt 
sqledecl 
sqlebutm 
sqlubComplete 
sqlubRCleanup 
sqlubcka 
sqlubcka_route_in 
sqlerKnownProcedure 
sqlerCallDL 
sqljs_ddm_excsqlstt 
sqljsParse 
sqljsSqlam 
sqljsDriveRequests 
sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
sqeAgent::RunEDU 
sqlzRunEDU 
sqloEDUEntry 
 
This APAR will fix this memory access violation by changing the 
latching behavior.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 client users using multi-threaded ODBC application.      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to db2_v97fp10 or later releases.                    * 
****************************************************************
Local-Fix:
Lösung
db2_v97fp10 contains this fix. After fix, we don't see any 
crash.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.05.2014
10.11.2014
10.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.10 FixList