|
Problem IT04121
|
Status: Closed |
DB2 MAY CRASH UNDER SQLRIBNO IF AN INTERNAL RECORD IS SELECTED AS PART OF A RIDLIST SCAN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
DB2 may crash under sqlribno if an internal record is selected
as part of a RIDLIST scan
The stack will be similar to:
memcpy
sqlribnoCb
sqlribno
sqlriExecSargThread
sqldEvalDataPred
sqldGetXMLDocument
sqldRowFetch
sqlriListFetch
sqlriSectInvoke
...
This APAR fix will introduce processing to skip over internal
records allowing the scan to continue unimpeded.
This situation is more likely to occur if the RIDLIST_SCAN takes
a long time to run and will only happen if an internal record
gets written or moved during the time the scan is open causing
the rdilist scan to unintentionally attempt to see the internal
record as data.
Under normal data (ridlist_scan) conditions there should be no
way that a page dictionary slot is part of the scan nor should a
page dictionary slot be interpreted to be a data slot. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in Version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.09.2014
04.08.2015
04.08.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
