DB2 - Problem description
Problem IC84424 | Status: Closed |
DB2APP.DLL HAS CAUSED A STACK OVERFLOW EXCEPTION (0XC00000FD) WHEN TRYING TO WRITE TO MEMORY LOCATION 0X00032FFC ON THREAD 0 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If your application is prepared with the CONNECT 2 option and is stopped by a db2 force application, a network problem or a db2stop, your application may go in a rollback loop and may end up crashing with a stack overflow exception instead of returning the expected error -1224. (SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated your particular request due to a problem with your request) This is an example of the stack that you might have : DB2APP!SQLJRPOSTERRORPROCESSING+4AIn MINIDUMP_FirstChance_sov_StackOverflow_PROG.exe__1c2c_2011-06-1 7_09-52-50-548_1c44.dmp the assembly instruction at db2app!sqljrPostErrorProcessing+4a in C:\Program Files\IBM\SQLLIB\BIN\db2app.dll has caused a stack overflow exception (0xC00000FD) when trying to write to memory location 0x00032ffc on thread 0 Function Arg 1 Arg 2 Arg 3 Source db2app!sqljrPostErrorProcessing+4a 03401e80 033ef8e0 81360068 sqljraux.C @ 2517 + bdc db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00033478 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00033728 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 000339d8 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00033c88 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00033f38 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 000341e8 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00034498 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00034748 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 000349f8 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00034ca8 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00034f58 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00035208 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 000354b8 00000000 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 81360068 db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 00035768 00000000 sqljrintrfc.C @ 6758 <snip about 2000 lines> db2app!?sqljrDrdaAr2PRollback.@@YAHPAUdb2UCinterface@@@Z+22b 033ef8e0 0012de38 02c7b318 sqljrintrfc.C @ 6758 db2app!_VInfreq_?sqljrPostErrorProcessingYAXPAUsqljrDrdaArCbPAUd b2UCinterfaceHZ+204 03401e80 033ef8e0 8136001c db2app!sqljrDrdaArExecute+38a 033ef8e0 00000000 00000000 db2app!sqlacall+8ea 00000018 0000000d 00000002 STARe+5ecb20 02c7afc0 0012e428 0012e7b8 STARe+5f611d 02c7afc0 2543cc5b 0012e7b8 STARe+70dd59 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 FP1 or later * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 10.1 FP1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 11.02.2013 11.02.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |