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

INSTANCE SUSPENDED DUE TO SIG #11, FUNCTION
SQLNG_PROCESS_FETCH_OP, LINE NUMBER 6139

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
I am working on db2_v97fp1 aix64 n090625 DPF instance(4 LNs) 
executing some DML operations on the database. My instance 
suspended . 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x090000001ABA8E4C 
sqlng_process_fetch_op__FP9sqlng_blkP19sqlno_plan_operator + 
0xE4C 
0x09000000173AE5F4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x434 
0x090000001AB855A4 
sqlng_process_tq_op__FP9sqlng_blkP19sqlno_plan_operator + 0x8A4 
0x090000001ABB3270 
sqlng_process_return_op__FP9sqlng_blkP19sqlno_plan_operator + 
0xAF0 
0x09000000173AE490 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x2D0 
0x090000001AA8ABE8 sqlng_main__FP9sqlnq_qur + 0x28A8 
0x0900000019C7D854 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur 
+ 0x7194 
0x0900000019C7F644 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env 
+ 0x64 
0x0900000019C6BADC 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPiPUl 
+ 0x163C 
0x0900000019C45C48 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 
SQLP_LOCK_INFOPP16sqlra_cached_varT12_PUlb 
+ 0xD48 
0x0900000019C12FA8 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x2028 
0x0900000018F053CC 
sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x24C 
0x090000001C759DA8 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x1A8 
0x090000001888E3C8 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface 
+ 0x208 
0x090000001888CFFC 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x1FC 
0x090000001884F954 sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 
0x494 
0x090000001885177C 
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x15C 
0x0900000018858740 
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x460 
0x090000001885A7BC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x23C 
0x0900000016E54D4C RunEDU__8sqeAgentFv + 0x3AC 
0x0900000016E448BC EDUDriver__9sqzEDUObjFv + 0x19C 
0x0900000016E44BDC sqlzRunEDU__FPcUi + 0x3C 
0x0900000016D4BBA4 sqloEDUEntry + 0x6A4 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users will see a trap in certain scenarios.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* 1. We are in an error handling path and we are trying to     * 
* access some data structure that was created on stack and is  * 
* now no longer in scope.                                      * 
* 2. Fix is to make sure the data structure is not accessed in * 
* the error path.                                              * 
* 3. Problem has been in code, but it is difficult to          * 
* reproduce - as we need to hit an error at the right point    * 
* i.e. if we encounter an error at some other point, we might  * 
* not run into this problem. (tho' in this SVT scenario, the   * 
* tester has been able to reproduce it multiple times)         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 FP1.                                         * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Fix was checked into v9.7 FP1. 
Trap has been fixed.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.07.2009
04.01.2010
04.01.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList