home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
15.0.xC1.2 FixList
14.10.xC13.3 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 IT09544 Status: Geschlossen

ONSTAT -G SES REPORTS SESSION POOL OPENTABLE MEMORY LEAK WHEN RUNNING
QUERIES WHICH REQUIRE AUTO-INDEX PATH QUERY PLANS

Produkt:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problembeschreibung:
This problem appears to be new in 12.10.FC5 (as it did not 
reproduce in 12.10.FC4). 
 
Query plan for the query being run repeatedly is as follows 
(showing it's using auto-index path) 
 
select {+ ORDERED, AVOID_HASH(t2), AVOID_FULL(t2) } * 
from t1,t2 
where t1.c1 = 1 and t1.c2 = 5 and 
t1.c2 = t2.c2 
 
DIRECTIVES FOLLOWED: 
ORDERED 
AVOID_HASH ( t2 ) 
AVOID_FULL ( t2 ) 
DIRECTIVES NOT FOLLOWED: 
 
Estimated Cost: 7 
Estimated # of Rows Returned: 2 
 
  1) jrenaut.t1: INDEX PATH 
 
    (1) Index Name: jrenaut.t1_idx1 
        Index Keys: c1 c2 c3   (Key-Only)  (Serial, fragments: 
ALL) 
        Lower Index Filter: (jrenaut.t1.c2 = 5 AND jrenaut.t1.c1 
= 1 ) 
 
  2) jrenaut.t2: AUTOINDEX PATH 
 
    (1) Index Name: (Auto Index) 
        Index Keys: c2 
        Lower Index Filter: jrenaut.t1.c2 = jrenaut.t2.c2 
NESTED LOOP JOIN 
 
Then if you use onstat -g ses <session id> to monitor the 
session's memory pool you will see the opentable size growing. 
 
Sample output: 
 
Memory pools    count 3 
name         class addr              totalsize  freesize 
#allocfrag #freefrag 
45           V     462ec040         15519744   11314272   3935 
7501 
45*O0        V     461b8040         4096       768        1 
1 
45_SORT_0    V     4618d040         69632      52096      87 
88 
 
name           free       used           name           free 
used 
overhead       0          9984           scb            0 
144 
opentable      0          4066232        filetable      0 
1232 
 
Then to distinguish this from other opentable session growth 
(like APAR IT03000) if you do onstat -g afr <session id> | grep 
opentab you will see an increasing amount of lines that look 
like this: 
 
4eec1630         1080       opentable    3669   rssupp.c:224 
4eec3630         1080       opentable    3669   rssupp.c:224 
4eec5630         1080       opentable    3669   rssupp.c:224 
4eec7630         1080       opentable    3669   rssupp.c:224 
4eec9630         1080       opentable    3669   rssupp.c:224 
4eecb630         1080       opentable    3669   rssupp.c:224 
4eecd630         1080       opentable    3669   rssupp.c:224 
4eecf630         1080       opentable    3669   rssupp.c:224 
4eed1630         1080       opentable    3669   rssupp.c:224 
4eed3630         1080       opentable    3669   rssupp.c:224 
4eed5630         1080       opentable    3669   rssupp.c:224 
4eed7630         1080       opentable    3669   rssupp.c:224 
4eed9630         1080       opentable    3669   rssupp.c:224 
4eedb630         1080       opentable    3669   rssupp.c:224 
4eedd630         1080       opentable    3669   rssupp.c:224 
4eedf630         1080       opentable    3669   rssupp.c:224 
4eee1630         1080       opentable    3669   rssupp.c:224
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* IDS.12.10.xC5 users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10.xC6                      * 
****************************************************************
Local-Fix:
Lösung
Problem Fixed In IBM Informix Server 12.10.xC6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.06.2015
30.12.2015
30.12.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
12.10.xC6
Problem behoben lt. FixList in der Version
12.10.xC6 FixList