|
Problem IC66552
|
Status: Closed |
POSSIBLE PANIC IN SQLDUNSETPUNC, PROBE:12991 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During a row fetch, a panic may occur and the db2diag.log
indicates Severe error at
probe 12991 in function sqldUnsetPunc.
2009-09-15-22.09.22.570383-240 I136989991E1721 LEVEL:
Severe
PID : 20366 TID : 47538820344128 KTID :
21346
PROC : db2sysc 2
INSTANCE: svtdbm8 NODE : 002 DB : DJDB
APPHDL : 2-482 APPID: *N2.svtdbm8.090916020917
AUTHID : SVTDBM8
EDUID : 83 EDUNAME: db2agent (DJDB) 2
FUNCTION: DB2 UDB, data management, sqldUnsetPunc, probe:12991
MESSAGE : Invalid record header offset ... record offset:
DATA #1 : Pointer, 8 bytes
0x00002b3c80f6107c
DATA #2 : String, 31 bytes
address of start of data page:
DATA #3 : Pointer, 8 bytes
0x00002b3c5842b030
DATA #4 : String, 35 bytes
first byte after data page header:
DATA #5 : Pointer, 8 bytes
0x00002b3c5842b046
DATA #6 : String, 17 bytes
data page space:
DATA #7 : unsigned integer, 8 bytes
32700
DATA #8 : String, 15 bytes
Record header:
DATA #9 : Hexdump, 4 bytes
0x00002B3C80F6107C : 0200 B0FA
....
CALLSTCK:
[0] 0x00002B3C2989AFB1 pdLog + 0x1ED
[1] 0x00002B3C29DF287B
_Z13sqldUnsetPuncP13SQLD_DFM_WORKP12SQLD_REC_HDRh + 0x3A1
[2] 0x00002B3C29E1E084 _Z15sqldLockForReadP8SQLD_CCB + 0x46E
[3] 0x00002B3C2C218742 _Z14sqlriLockTableP8sqlrr_cb + 0x14C
[4] 0x00002B3C29DF7D46
_Z21sqlriExecSimpleThreadP8sqlrr_cbP12sqlri_opparm + 0x45E
[5] 0x00002B3C29E5F3C5
_Z16sqldEvalDataPredP13SQLD_DFM_WORKPmP10SQLD_DPRED + 0x281
[6] 0x00002B3C29E6410E _Z12sqldReadNormP13SQLD_DFM_WORKl +
0x1998
[7] 0x00002B3C29E64D5D /home/svtdbm8/sqllib/lib64/libdb2e.so.1
+ 0x1660D5D
[8] 0x00002B3C29E6691F _Z7sqldfrdP13SQLD_DFM_WORK + 0xF47
[9] 0x00002B3C29DEC53C
_Z12sqldRowFetchP8sqeAgentP8SQLD_CCBmmPP10SQLD_VALUEP8SQLZ_RIDmP
12SQLD_ID_LISTP9SQLP_LSN8
+ 0x16
CA |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* A Panic occurs and the db2diag.log indicates Severe error at *
* probe 1291. *
* *
* *
* 2009-09-15-22.09.22.570383-240 I136989991E1721 LEVEL: *
* Severe *
* PID : 20366 TID : 47538820344128 KTID : *
* 21346 *
* PROC : db2sysc 2 *
* INSTANCE: svtdbm8 NODE : 002 DB : *
* DJDB *
* APPHDL : 2-482 APPID: *
* *N2.svtdbm8.090916020917 *
* AUTHID : SVTDBM8 *
* EDUID : 83 EDUNAME: db2agent (DJDB) 2 *
* FUNCTION: DB2 UDB, data management, sqldUnsetPunc, *
* probe:12991 *
* MESSAGE : Invalid record header offset ... record offset: *
* DATA #1 : Pointer, 8 bytes *
* 0x00002b3c80f6107c *
* DATA #2 : String, 31 bytes *
* address of start of data page: *
* DATA #3 : Pointer, 8 bytes *
* 0x00002b3c5842b030 *
* DATA #4 : String, 35 bytes *
* first byte after data page header: *
* DATA #5 : Pointer, 8 bytes *
* 0x00002b3c5842b046 *
* DATA #6 : String, 17 bytes *
* data page space: *
* DATA #7 : unsigned integer, 8 bytes *
* 32700 *
* DATA #8 : String, 15 bytes *
* Record header: *
* DATA #9 : Hexdump, 4 bytes *
* 0x00002B3C80F6107C : 0200 B0FA *
* .... *
* CALLSTCK: *
* [0] 0x00002B3C2989AFB1 pdLog + 0x1ED *
* [1] 0x00002B3C29DF287B *
* _Z13sqldUnsetPuncP13SQLD_DFM_WORKP12SQLD_REC_HDRh + 0x3A1 *
* [2] 0x00002B3C29E1E084 _Z15sqldLockForReadP8SQLD_CCB + *
* 0x46E *
* [3] 0x00002B3C2C218742 _Z14sqlriLockTableP8sqlrr_cb + *
* 0x14C *
* [4] 0x00002B3C29DF7D46 *
* _Z21sqlriExecSimpleThreadP8sqlrr_cbP12sqlri_opparm + 0x45E *
* [5] 0x00002B3C29E5F3C5 *
* _Z16sqldEvalDataPredP13SQLD_DFM_WORKPmP10SQLD_DPRED + 0x281 *
* [6] 0x00002B3C29E6410E _Z12sqldReadNormP13SQLD_DFM_WORKl + *
* 0x1998 *
* [7] 0x00002B3C29E64D5D *
* /home/svtdbm8/sqllib/lib64/libdb2e.so.1 + 0x1660D5D *
* [8] 0x00002B3C29E6691F _Z7sqldfrdP13SQLD_DFM_WORK + 0xF47 *
* [9] 0x00002B3C29DEC53C *
* _Z12sqldRowFetchP8sqeAgentP8SQLD_CCBmmPP10SQLD_VALUEP8SQLZ_RID
* + 0x16 *
* CA *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v9.07.002 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
|
| Solution |
Problem is first fixed in DB2 UDB version 9.7 fix pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.02.2010
03.05.2010
03.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.7.002,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
