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

AFTER A CRASH IN TSMAPI64.DLL, SUBSEQUENT DB2START FAILS.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Platform: Windows 2008 64bit 
DB2: DB2 v9.7fp6 
Pre-req: Access violation in TSMAPI64 causes db2syscs to crash. 
 
Subsequent db2starts fails with access violation in sqloMLNique 
with callstack as the following: 
 
<sqloMLNique> <NT\sqloque.C:834> 
<sqloTQMStartMLN> 
<E:\db2_v97fp6\ntx64\s120629\engn\include\sqlotqm.h:110> 
<sqlccipcconnmgr_child> <sqlccipc_srv.C:458> 
<sqloEDUEntry> <sqloedu.C:3454>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on Windows                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp8                                        * 
****************************************************************
Local-Fix:
Resolve the TSMAPI64 problem, then the db2start problem will not 
happen.
verfügbare FixPacks:
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_v97fp8
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.04.2013
02.04.2013
22.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList