DB2 - Problembeschreibung
Problem IT04121 | Status: Geschlossen |
DB2 MAY CRASH UNDER SQLRIBNO IF AN INTERNAL RECORD IS SELECTED AS PART OF A RIDLIST SCAN | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 5. * **************************************************************** | |
Local-Fix: | |
Lösung | |
First fixed in Version 10.1 Fix Pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.09.2014 04.08.2015 04.08.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |
![]() |