INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70

Using the bts_contains function in a Select query like this 
 
SELECT   gem_intern_id  FROM c_d_gemeente  WHERE 
    bts_contains(gem_naam, "Sint-pieters(") 
 
The query returns an error -937 as expected. When the query 
is running in a transaction and is executed again and again 
without closing the Transaction the Memory pool for the 
transaction is growing. 
 
TRX.72066.7  VX    7000000b0020040  12701696         5592 
102725     5 
TRX.72066.7  VX    7000000b0020040  19587072         7232 
158475     6 
 
Using a similar query which does not return an error in the 
bts_contains does not 
show a memory growth in the RTX memory pool.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users that are running a hundred or thousands of             * 
* bts_contain() predicates that have a bad query expression    * 
* parameter.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommend fixing the bad contains predicate as it is very    * 
* costly to run a bts_contains scan to only generate           * 
* exceptions.  After the exception the transaction can be      * 
* closed with a commit or rollback and a new transaction       * 
* started and then the partially built up query in Clucene     * 
* memory would have been released.  Future releases of the     * 
* informix product will have a fix for the memory leak on a    * 
* bad query.  NOTE:  There was no memory leak with properly    * 
* formed queries.                                              * 
****************************************************************

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

05.01.2015
16.10.2015
16.10.2015