IBM Support

IT06378: MEMORY LEAK IN GEO-SPATIAL CALLS WHILE ACCESSING SPECIFIC TYPE OF DATA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • There is a memory leak which are triggered by Geo-spatial
    function calls such as st_intersects() when run on specific
    types of data. The symptoms are shown in:
    
    a) top output ( The RES - SHR value for db2sysc would be
    unusually large ) OR
    b) ps -elf output will show an unusually large size for the
    db2sysc pid and it will slowly keep growing AND
    c) db2pd -memb pid=<db2sysc pid> will show OSSe blocks allocated
    with LOC 43 or 60 and File 0.
    
    A snippet of the output from db2pd -memb output:
    
    Address            DataAddress        PoolID     PoolName
    BlkAge Size(Bytes)  I LOC   File
    0x00002AABEE9008E0 0x00002AABEE9008F0 OSSe       OSSe
    OSSe       304          1 43         0
    0x00002AABEE900A40 0x00002AABEE900A50 OSSe       OSSe
    OSSe       296          1 43         0
    0x00002AABEE900B90 0x00002AABEE900BA0 OSSe       OSSe
    OSSe       296          1 43         0
    0x00002AABEE900CE0 0x00002AABEE900CF0 OSSe       OSSe
    OSSe       320          1 43         0
    0
    ..
    ..
    Total set size: 880888 bytes
    
    Memory blocks sorted by size:
    PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File
    OSSe       OSSe       880888               2723       43    0
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 v9.7 FP11                                     *
    ****************************************************************
    

Problem conclusion

  • Fixed in DB2 v9.7 FP11
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT06378

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-08

  • Closed date

    2015-10-13

  • Last modified date

    2015-10-13

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

    IT06307

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 October 2015