|
Problem IT17214
|
Status: Closed |
THE DATABASE MIGHT ABEND DUE TO PROGRAMMING ERROR IN LIST PREFETCH PROCESSING. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
The symptom of the problem is following entry in the
db2diag.log:
2016-09-11-05.57.09.988817+000 I155200947E1183 LEVEL:
Severe
PID : 39281 TID : 140468423747328 PROC :
db2sysc 47
INSTANCE: db2inst1 NODE : 047 DB :
SAMPLE
APPHDL : 0-53118 APPID:
10.10.10.100.41775.160911055257
AUTHID : DB2INST1 HOSTNAME: sl55edwdbp13
EDUID : 233782 EDUNAME: db2agnts (SAMPLE) 47
FUNCTION: DB2 UDB, data management, sqldmPrefetchList,
probe:1966
MESSAGE : LIST PREFETCH in reverse: 1190 32 ...
DATA #1 : Hexdump, 128 bytes
0x00007FD458E7C4E0 : A604 0000 2000 0000 2100 0000 2200 0000
.... ...!..."...
0x00007FD458E7C4F0 : 2300 0000 2400 0000 2500 0000 2600 0000
#...$...%...&...
0x00007FD458E7C500 : 2700 0000 2800 0000 2900 0000 2A00 0000
'...(...)...*...
0x00007FD458E7C510 : 2B00 0000 2C00 0000 2D00 0000 2E00 0000
+...,...-.......
0x00007FD458E7C520 : 2F00 0000 3000 0000 3100 0000 3200 0000
/...0...1...2...
0x00007FD458E7C530 : 3300 0000 3400 0000 3500 0000 3600 0000
3...4...5...6...
0x00007FD458E7C540 : 3700 0000 3800 0000 3900 0000 3A00 0000
7...8...9...:...
0x00007FD458E7C550 : 3B00 0000 3C00 0000 3D00 0000 3E00 0000
;...<...=...>...
...
Consequence of above is FODC processing where in the stack we
might observe (snippet):
...
sqloDumpEDU
sqldDumpContext
sqlrr_dump_ffdc
sqlzeDumpFFDC
sqlzeMapZrc
sqlrrMapZrc
sqlriPrefetchRIDs
sqlriListFetch
qlrihsjn
qlrihsjn
sqlriSectInvoke
...
Eventually, the problem is causing DB to be marked bad. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
During error processing, DB2 logs in the db2diag.log SQL
statement:
2016-09-11-05.57.10.035954+000 I155203356E12407 LEVEL:
Severe
PID : 39281 TID : 140468423747328 PROC :
db2sysc 47
INSTANCE: db2inst1 NODE : 047 DB :
SAMPLE
APPHDL : 0-53118 APPID:
10.10.10.100.41775.160911055257
AUTHID : DB2INST1 HOSTNAME: sl55edwdbp13
EDUID : 233782 EDUNAME: db2agnts (SAMPLE) 47
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling,
probe:140
MESSAGE : section stmt
DATA #1 : Hexdump, 2338 bytes
0x00007FD4649ED7A0 : 7365 6C65 6374 2061 3137 2E4D 5243 485F
select A10.MYTAB
...
Look to avoid statement causing the issue. |
| available fix packs: |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
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 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2016
09.05.2017
09.05.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 11.1.1.1
|
 |
