DB2 - Problembeschreibung
Problem IT16869 | Status: Geschlossen |
SELECT ROW CHANGE TOKEN WILL RETURN WRONG RESULT WHEN USING RIDSCAN (ROW IDENTIFIER SCAN) | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
SELECT ROW CHANGE TOKEN will return wrong result when using RIDSCAN (Row Identifier Scan) e.g.: following sql will return wrong result when using RIDSCAN ( (Row Identifier Scan) => db2 "select row change token for bas.QUEUEINFO_20160723 FROM bas.QUEUEINFO_20160723 where id < 4467" 1 -------------------- 0 0 0 0 0 0 0 0 0 0 ... 0 0 140 record(s) selected. Access Plan like following: ----------- Total Cost: 36.5867 Query Degree: 1 Rows RETURN ( 1) Cost I/O | 140.456 FETCH ( 2) 36.5629 33 /----+-----\ 140.456 4922 RIDSCN TABLE: BAS ( 3) QUEUEINFO_20160723 6.9544 Q1 1 | 140.456 SORT ( 4) 6.95392 1 | 140.456 IXSCAN ( 5) 6.91635 1 | 4922 INDEX: SYSIBM SQL160808050052790 Q1 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please, see error description and install this Fix. * **************************************************************** | |
Local-Fix: | |
Use an optimizer guideline to choose a different access, like IXSCAN: <IXSCAN TABLE='tablename_in_query'/> | |
verfügbare FixPacks: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Lösung | |
Please, see error description and install this Fix. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.09.2016 16.07.2018 16.07.2018 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
11.1.1.1 |