So far, the problem has only been observed in 32 bit DB2
instances running on 32 bit releases of SUSE Linux Enterprise
Server (SLES) 11. A vectored read issued by a prefetcher may
fail with the following symptoms present in the DB2 diagnostic
log file:
2013-07-24-15.27.06.351845-240 I22615G1300 LEVEL: Error
PID : 9249 TID : 2874141552 PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
HOSTNAME: myhostname
EDUID : 47 EDUNAME: db2pfchr (SAMPLE)
FUNCTION: DB2 UDB, oper system services, sqloReadVLow, probe:100
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic
error detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : Codepath, 8 bytes
7:9:25
DATA #2 : String, 17 bytes
preadv() failed !
DATA #3 : signed integer, 4 bytes
-1
DATA #4 : unsigned integer, 4 bytes
22
...or...
2013-07-24-15.27.06.519283-240 I26999G1294 LEVEL: Error
PID : 9249 TID : 2874141552 PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
HOSTNAME: myhostname
EDUID : 47 EDUNAME: db2pfchr (SAMPLE)
FUNCTION: DB2 UDB, oper system services, sqloReadVLow, probe:100
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not
exist"
DIA8506C Unexpected end of file was reached.
DATA #1 : Codepath, 8 bytes
7:17:27
DATA #2 : String, 17 bytes
End of file hit !
DATA #3 : signed integer, 4 bytes
0
DATA #4 : unsigned integer, 4 bytes
22
In many cases, these errors will pass unnoticed with no impact,
and the only way to discover them is to check the DB2 diagnostic
log file. However, there are known scenarios where an impact
will become visible:
- failures during a database backup (typically SQL0902C)
- SQL termination errors during application processing |
