|
Problem IC98875
|
Status: Closed |
QUERY ON PARTITIONED TABLE MIGHT FAIL WITH SQLD_BADPAGE AND SQLDFETCHDIRECT PROBE: 5395 ERRORS WHEN RUNNING EHL |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In DB2 pureScale instances running Explicit Hierarchical Locking
(EHL), a query against a partitioned table with a
non-partitioned index might fail with a "bad page" error due to
a timing problem. You will see a message similar to the
following in the db2diag.log file:
2014-01-05-13.11.42.437771-300 I6989043A598 LEVEL:Severe
PID : 33489138 TID : 55538 KTID :80871449
PROC : db2sysc 1
INSTANCE: db2test NODE : 001 DB :SAMPLE
APPHDL : 1-305 APPID:9.26.94.187.52646.140105181118
AUTHID : DB2TEST HOSTNAME: testxxxx
EDUID : 55538 EDUNAME: db2agent (SAMPLE) 1
FUNCTION: DB2 UDB, data management, sqldFetchDirect, probe:5395
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
Page" DIA8500C A data file error has occurred, record id is "". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of EHL with partitioned tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
Either disable EHL by setting the OPT_DIRECT_WRKLD database
configuration parameter to "NO" or by dropping the
non-partitioned index. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.01.2014
27.02.2014
07.04.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
