DB2 - Problembeschreibung
Problem IT08816 | Status: Geschlossen |
INCORRECT RESULTS FROM SORT OPERATIONS ON DB2 VERSION 9.7.0.10 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Incorrect results from sort operations might occur when all of the following conditions are true: - DB2 version 9.7.0.10 (or a special build containing an incorrect fix for APAR IT00913) is being used. - The sort operation includes more than one column. - The sort operation includes one or more VARCHAR or VARCHAR FOR BIT DATA columns beyond the first column. - The sort operation includes more than 500 records containing duplicate data in the columns leading up to the VARCHAR column. In addition to potential wrong and/or incorrectly ordered results being returned to the user based on incorrect sort order, it is also possible that the incorrect sort could result in an unordered index if the index was created or rebuilt using the problematic version of DB2. This could result in the following symptoms: - Index errors during insert, update or delete processing. - Incorrect results from an index scan. - Duplicates being inserted into a unique index. The db2dart command can be used to detect any unordered indexes. This problem does not exist in v10.1. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7.0.11. * **************************************************************** | |
Local-Fix: | |
To avoid hitting the problem while on an affected built, execute the following command and then recycle the instance: db2set DB2_BINSORT=off After applying the workaround above and/or moving to a build with this APAR fix, to fix an affected index, execute the command above, recycle the instance and then perform one of the following actions: - Drop and recreate the affected index(es). - Execute the REORG INDEXES command without the CLEANUP ONLY option to rebuild the affected index(es). | |
Lösung | |
The problem is first fixed in DB2 version 9.7.0.11. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.05.2015 12.10.2015 29.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.0.11 | |
Problem behoben lt. FixList in der Version | |
9.7.0.11 |