IBM Support

IT06304: USING BTS_SEARCH IN A QUERY WHICH RETURNS AN ERROR CAUSES A MEMORY LEAK IN THE TRX SESSION POOL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • 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.
    

Local fix

Problem summary

  • ****************************************************************
    * 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.                                              *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT06304

  • Reported component name

    INFORMIX SERVER

  • Reported component ID

    5725A3900

  • Reported release

    B70

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-05

  • Closed date

    2015-10-16

  • Last modified date

    2015-10-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • RC10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 October 2015