DB2 - Problembeschreibung
Problem IC68030 | Status: Geschlossen |
FAILURE DURING A FETCH FROM A CURSOR MAY CAUSE AN INSTANCE CRASH WITH SIGNAL SEGV IN DPF ENVIRONMENT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
The following message in the db2diag.log file is a good indication for this APAR: 2010-04-16-02.40.10.789349+120 I9112264A556 LEVEL: Severe PID : 5566472 TID : 21253 PROC : db2sysc INSTANCE: xxxxx NODE : 998 DB : DB APPHDL : 998-58929 APPID: yyyyy AUTHID : zzzzz EDUID : 21253 EDUNAME: db2agent (DB) 998 FUNCTION: DB2 UDB, runtime interpreter, sqlriecc, probe:25 MESSAGE : sosptr NULL on close, logging open flag and sibling->sectptr! DATA #1 : unsigned integer, 4 bytes 2 DATA #2 : Pointer, 8 bytes 0x0700000027c47b00 Signal SGEV is triggered by the following stack trace: 0x09000000047311F8 sqlriCleanLobBlockingCB__FP8sqlrr_cb + 0x14C 0x0900000003B641D0 sqlricls_complex__FP8sqlrr_cbilN23 + 0x108 0x0900000003D67F9C @87@sqlricls__FP8sqlrr_cbiN32 + 0x64 0x09000000043D94E8 sqlriecc__FP8sqlrr_cbilT3 + 0x102C 0x09000000044A40B8 sqlriecc__FP8sqlrr_cbilT3@glueDBD + 0x74 0x0900000003FAE540 sqlrr_process_close_request__FP8sqlrr + 0x548 0x090000000409C96C sqlrr_process_close_request__FP8sqlrr + 0x80 0x0900000003B9EEFC sqlrr_rds_common_post__FP14db2UCint + 0xFE4 0x0900000003BD4418 sqlrr_fetch__FP14db2UCinterface + 0x71C 0x0900000003BD4F98 sqljs_ddm_cntqry__FP14db2UCinterface + 0x900 .... | |
Problem-Zusammenfassung: | |
USERS AFFETCED: All PROBLEM DESCRIPTION: See ERROR DESCRIPTION PROBLEM SUMMARY: See ERROR DESCRIPTION | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.5 Fix Pack 6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC68032 IC68033 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 20.04.2010 10.09.2010 10.09.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |