Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC73936 Status: Closed

SEVERE SQLDREADTABLEINFO DB2DIAG.LOG FOR INTERRUPTED QUERY.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After a query was interrupted, the db2diag.log may report : 
 
2011-01-13-04.40.25.716609+000 I1286353A7696      LEVEL: Severe 
PID     : 29229284             TID  : 22296       PROC : db2sysc 
2 
INSTANCE: db2inst1          NODE : 002         DB   : SAMPLE 
APPHDL  : 0-19566            APPID: 
9.122.128.160.57849.101213022 
AUTHID  : db2inst1 
EDUID   : 22296                EDUNAME: db2agntp (SAMPLE) 2 
FUNCTION: DB2 UDB, data management, sqldReadTableInfo, 
probe:10089 
MESSAGE : Fail positioning record within the page 
DATA #1 : Hexdump, 1424 bytes 
0x0700000115BFC720 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0700000115BFC730 : 0000 0000 2010 0000 0000 0000 0000 0000 
.... ........... 
0x0700000115BFC740 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0700000115BFC750 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
... 
 
The message is misleading as it does not indicate a serious 
problem and only appears if a statement is accessing a table and 
 
is interrupted whilst doing so. The problem is timing dependent 
and should not be seen very regularly. 
The db2diag.log message is the only symptom, as the interrupt is 
further handled correctly.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Misleading and incorrect severe error message raised in the  * 
* db2diag.log coming from function SQLDREADTABLEINFO           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade DB2 to V9.7 fixpak 4                                 * 
****************************************************************
Local Fix:
available fix packs:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in V9.7 Fixpak 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.01.2011
24.05.2011
24.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.