home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC91228 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
available fix packs:
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_v97fp8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.04.2013
02.04.2013
22.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.3 FixList
10.1.0.3 FixList