| Neueste Versionen | FixList |
| 14.10.xC10 |
 |
| 12.10.xC16.X5 |
|
| 11.70.xC9.XB |
|
| 11.50.xC9.X2 |
|
| 11.10.xC3.W5 |
|
| Haben Sie Probleme? - Kontaktieren Sie uns. | |
| Kostenlos registrieren |
|
| Kontaktformular |
|
Informix - Problembeschreibung
| Problem IT27566 | Status: Geschlossen |
RANGE FRAGMENTED TABLE WITH FRAGMENT LEVEL STATISTICS CAN HAVE NEGATIVE COUNT IN BIN AFTER UPDATE STATISTICS MEDIUM | |
| Produkt: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
| Problembeschreibung: | |
After an update statistics medium on a range fragmented table
you may observe queries failing with error:
768: Internal error in routine sqoptim: no valid query plan
generated.
In this case the table is range fragmented and has fragment
level statistics. After an update statistics medium a negative
value in a bin of the distribution information is observed:
Medium Mode, 2.500000 Resolution, 0.950000 Confidence
--- DISTRIBUTION ---
( 1)
1: (-16213, 12, 43)
2: ( 28, 3, 178)
--- OVERFLOW ---
1: ( 24010, 1)
2: ( 3211, 2)
3: ( 1456, 3)
4: ( 599, 4)
5: ( 180, 5)
6: ( 258, 6)
7: ( 124, 7)
Another run of update statistics medium might cure this. If that
is not the case an update statistics high could be considered
(please remember to use the FORCE option if necessary). | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of IDS prior to 12.10.xC12. * **************************************************************** * PROBLEM DESCRIPTION: * * Range fragmented table with fragment level statistics can * * have negative count in bin after update statistics medium. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
| Local-Fix: | |
| Lösung | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 26.12.2018 04.10.2019 04.10.2019 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
12.10.xC12 | |
| Problem behoben lt. FixList in der Version | |
