home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

Informix - Problembeschreibung

Problem IT04708 Status: Geschlossen

WITH BATCHEDREAD_INDEX = 0 AND A NON-LOGGED DATABASE, CERTAIN INDEX
CORRUPTION COULD MAKE A SQLEXEC THREAD RUN IN A TIGHT LOOP

Produkt:
IFMX ULT WHSE E / IM0019BOS / C10 - IDS 12.10
Problembeschreibung:
When BATCHEDREAD_INDEX is turned off (so set to 0) and a query 
is on a non-logged database, if an index is corrupted in such a 
way so that the key value exists in the index, bu the rowid for 
the key no longer exists in the table (so the home row is 
already deleted), the query will hang and get stuck in a tight 
loop and tie up a cpu vp. 
 
The top portion of the stack for the thread would look something 
like this: 
 
#0  in buffget () 
#1  in phposition () 
#2  in rsread () 
#3  in fmread () 
#4  in gettupl () 
#5  in scan_next ()
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DB Users                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IDS-12.10.xC5                                      * 
****************************************************************
Local-Fix:
Lösung
Problem Fixed In IDS-12.10.xC5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.10.2014
16.10.2015
16.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
12.10.xC5 FixList
12.10.xC5.W1 FixList