|
Problem IT20869
|
Status: Closed |
DB2 CLIENT APPLICATION ON WINDOWS MAY CRASH IN WINDOWS' FUNCTIONCALLED FROM DB2SYS!SQLZDB2SYSDLL. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
DB2 client application loading db2sys.dll may crash in
windows function called from db2's dll entry point function (
db2sys!sqlzDb2SysDll ).
This problem may happen at time of exiting process or client
application unload db2sys.dll, which cause windows to invoke
db2's dll entry point function.
This happen due to the fact that db2sys!sqlzDb2SysDll was
using windows api that was internally not supported for using in
dll entry point function
( But not list in the list of function prohibited in dll
entry point function )
Following is the sample stack of the crash,
0061ed40 76ace66f user32!NtUserWaitMessage+0xc
0061ed88 76abae85 user32!DialogBox2+0x233
0061edb4 76aca4fa user32!InternalDialogBox+0x112
0061ee84 76ac9de6 user32!SoftModalMessageBox+0x8e2
0061eff0 76b05f7b user32!MessageBoxWorker+0x288
0061f070 76b06077 user32!MessageBoxTimeoutW+0x6c
0061f0a4 76b05e9b user32!MessageBoxTimeoutA+0xe3
0061f0c4 749e9882 user32!MessageBoxA+0x1a
0061f108 749e1c2c msvcr80!__crtMessageBoxA+0x1b4
[f:\dd\vctools\crt_bld\self_x86\crt\src\crtmbox.c @ 168]
0061f12c 749e16d0 msvcr80!_NMSG_WRITE+0x162
[f:\dd\vctools\crt_bld\self_x86\crt\src\crt0msg.c @ 242]
0061f134 749e2e3c msvcr80!_amsg_exit+0xe
[f:\dd\vctools\crt_bld\self_x86\crt\src\crt0dat.c @ 451]
0061f140 749e7021 msvcr80!_getptd+0x13
[f:\dd\vctools\crt_bld\self_x86\crt\src\tidtable.c @ 660]
0061f148 749f718a msvcr80!_LocaleUpdate::_LocaleUpdate+0x14
[f:\dd\vctools\crt_bld\self_x86\crt\src\setlocal.h @ 264]
0061f170 749f72b1 msvcr80!_strnicmp_l+0x1f
[f:\dd\vctools\crt_bld\self_x86\crt\src\strnicmp.c @ 59]
0061f18c 6ce0d838 msvcr80!_strnicmp+0x56
[f:\dd\vctools\crt_bld\self_x86\crt\src\strnicmp.c @ 138]
0061f3b0 6ce0d6c0 db2sys!sqlzDb2SysDll+0x1b6 [NT\sqlzinit.C @
170]
0061f3bc 775445f6 db2sys!sqlzDb2SysDll+0x3e [NT\sqlzinit.C @
263]
0061f3dc 77544643 ntdll_774f0000!LdrxCallInitRoutine+0x16
0061f424 775509a8 ntdll_774f0000!LdrpCallInitRoutine+0x60
0061f4c4 7755088d ntdll_774f0000!LdrShutdownProcess+0x18e
0061f4d8 76be3a8f ntdll_774f0000!RtlExitUserProcess+0x5f
0061f4ec 73993712 kernel32!ExitProcessImplementation+0x12
0061f774 739938c4
mscoreei!RuntimeDesc::ShutdownAllActiveRuntimes+0x2e8
0061f780 73494254
mscoreei!CLRRuntimeHostInternalImpl::ShutdownAllRuntimesThenExit
+0x13
0061f7b8 734941d7 clr!EEPolicy::ExitProcessViaShim+0x65
0061f9ec 733f7947 clr!SafeExitProcess+0x129
0061f9fc 733f798e clr!DisableRuntime+0x12e
0061fa10 7341ff48 clr!EEPolicy::HandleExitProcess+0x50
0061fa50 73422331 clr!_CorExeMainInternal+0x1b1
0061fa8c 7398f5a3 clr!_CorExeMain+0x4d
0061fac8 73a07f16 mscoreei!_CorExeMain+0x10a
0061fad8 73a04de3 mscoree!ShellShim__CorExeMain+0x99
0061fae0 76be8624 mscoree!_CorExeMain_Exported+0x8
0061faec 7754bd99 kernel32!BaseThreadInitThunk+0xe
0061fb30 7754bd6c ntdll_774f0000!__RtlUserThreadStart+0x72 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.06.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
