IBM Support

IC89149: FILE EVENT MONITOR LEAKS PRIVATE MEMORY WHEN FAILING TO WRITE OUT EVENT HEADER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A file event monitor may leak private memory when it fails to
    write out the header of a monitored event.  This may occur if
    the defined MAXFILESIZE / MAXFILES limit is reached or if
    filesystem space is exhausted.
    
    In the case of a deadlock event, if there is a large number of
    locks involved, the leaked memory may be large and cause memory
    usage problems on a system (eg. paging).
    
    A db2diag.log message is associated with the leak :
    EDUID   : 94323                EDUNAME: db2evmli (DEADLOCK_MON)
    0
    FUNCTION: DB2 UDB, database monitor, sqmEvmonBuffer::write_data,
    probe:10
    MESSAGE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor
    full of data"
              DIA8052C The Event Monitor "" has reached its file
    capacity. Delete
              the files in the target directory "" or move them to
    another
              directory.
    
    The memory growth occurs in the PERSISTENT_PRIVATE memory pool
    and can be monitored using the MON_GET_MEMORY_POOL monitor
    routine.
    
    db2pd -memblocks <db2sysc PID>
    may show a growing amount of memory allocations from a file ID
    of 3401466018:
    PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File
    0                     2272875936           1          4437
    3401466018
    0                     2272869259           1          4437
    3401466018
    ...
    

Local fix

  • Increase the MAXFILESIZE, MAXFILES attributes for the file event
    monitor and/or increase the filesystem space available to the
    event monitor
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * systems using file event monitors                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Use local fix or upgrade to DB2 Version 9.7 Fix Pack 8       *
    ****************************************************************
    

Problem conclusion

  • Problem first fixed in DB2 Version 9.7 Fix Pack 8
    

Temporary fix

  • see local fix
    

Comments

APAR Information

  • APAR number

    IC89149

  • 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

    2012-12-17

  • Closed date

    2013-07-11

  • Last modified date

    2013-07-11

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

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

    IC89151

Modules/Macros

  • sqm
    

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC89149

Modified date: 11 July 2013