IBM Support

IC77172: A SINGLE MONITORING EVENT, SUCH AS A DEADLOCK, CAN CREATE A FILE LARGER THAN WHAT IS SPECIFIED BY MAXFILESIZE.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Currently, a single monitoring event will be written to a new
    file if it does not fit in the current .evt file based on
    MAXFILESIZE.  However, the new file will be as large as needed
    to record the entire single event in one file.  This can result
    in a very large event file.
    
    The fix for this APAR provides an option to force an event
    record to fit into the target event file, up to the size defined
    by the MAXFILESIZE setting specified while creating the event
    monitor, by truncating the event record if necessary. So, for
    example, if a deadlock event dumps out a very large listing of
    locks, this information will be truncated to MAXFILESIZE.  The
    registry setting can be turned on and off by:
    
    db2set DB2_SYSTEM_MONITOR_SETTINGS=ENFORCE_MAX_FILE_SIZE:TRUE
    db2set DB2_SYSTEM_MONITOR_SETTINGS=ENFORCE_MAX_FILE_SIZE:FALSE
    
    db2stop
    db2start
    
    The default behavior will continue to be writing the entire
    event record into a single file without any truncation of data,
    thus allowing the size of the target .evt file to grow beyond
    the MAXFILESIZE setting.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 6.                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 version 9.7 Fix Pack 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77172

  • 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

    2011-06-27

  • Closed date

    2012-08-02

  • Last modified date

    2012-08-02

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

    IC76937

  • 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



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC77172

Modified date: 02 August 2012