DB2 - Problembeschreibung
Problem IC85201 | Status: Geschlossen |
HEAVY INDEX SCANNING CAUSED BY SQLD_NEED_RETRY CAN STARVE INSERT/DELETE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
On a heavily used table, with insert/update/delete activity and very heavy scanning (select) activity, it is possible for insert/delete to be left halfway through an update - with the data and index inconsistent. The response by scanners to this inconsistency is to get a SQLD_NEED_RETRY and retry its index scan. With many scanners, the page latch required by the update is constantly unavailable, with the result that the update is starved out for very long periods of time. The only external symptom will be a insert or delete statement that is taking too long. The only way to identify the issue is to take a trace using db2trc. The trace will show an insert or delete thread looping and repeatedly getting the SQLD_NEED_RETRY return code. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7.0.7. * **************************************************************** | |
Local-Fix: | |
If the select activity on the table slows or stops, the problem will resolve itself automatically. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Lösung | |
The problem is first fixed in DB2 version 9.7.0.7. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.07.2012 15.11.2012 15.11.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.0.7 | |
Problem behoben lt. FixList in der Version | |
9.7.0.7 |